You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"
The text was updated successfully, but these errors were encountered:
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:
return200onDeleteNonExisting=true
) - but file/resource is not deletedIn both cases I would expect "405 Method Not Allowed"
The text was updated successfully, but these errors were encountered: