Skip to content

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

Description

@oli-h

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"

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions