Skip to content

Throw HTTP 501 instead of 404 when request not supported #3075

@tuxick

Description

@tuxick

Is your feature request related to a problem? Please describe.

I noticed Android client requesting PDF preview which was not supported, leading to 404 error in web server log. This caused fail2ban to block the client. Wouldn't throwing a 501 Not Implemented be more sensible?

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions