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.

Sign up for GitHub

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

Jump to bottom

OData clients can trigger various 501 response codes #760

Open

alxndrsn opened this issue Oct 30, 2024 · 1 comment

Labels

backend bug nicer error

Contributor

alxndrsn commented Oct 30, 2024

The following OData errors look like they should be 4xx:

https://github.com/getodk/central-backend/blob/8b9db34bd91d03ca7d2f7719acc5363b1871ea03/lib/util/problem.js#L239-L242

5xx errors are for server-side issues
501 is for unsupported HTTP methods:

This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.
—https://www.rfc-editor.org/rfc/rfc9110#status.501

alxndrsn mentioned this issue

odata-filter: remove no-op case-change of function name getodk/central-backend#1237

Merged

matthew-white transferred this issue from getodk/central-backend

matthew-white added the backend label

Member

matthew-white commented Oct 30, 2024

I went ahead and transferred this issue, as it seems user-facing over the API.

matthew-white added nicer error bug labels

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