Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Storage 'filesystem': unexpected behaviour on "read only" filesystems #81

Open
oli-h opened this issue Sep 2, 2019 · 0 comments
Open

Comments

@oli-h
Copy link

oli-h commented Sep 2, 2019

In cases "read-only" or "write-protected" file/directory/filesystem (or simply: not enough access rights to create/delete/modify files and/or directories) the http-Response-Codes seem to be incorrect.
Examples:

  • DELETE on a write-protected file return "404 NOT FOUND" (or "200 OK" when return200onDeleteNonExisting=true) - but file/resource is not deleted
  • PUT of a resource onto a write-protected directory returns "500 internal server error"

In both cases I would expect "405 Method Not Allowed"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant