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
The API should have consistent and proper usage of HTTP error codes.
Right now wrong usage mostly results in an Internal Server Error (50x) and doesn't properly tell the user what went wrong. Furthermore, the API sometimes doesn't respond with an error code at all when obviously user input wasn't okay (see uploading files).
I would like to tackle that once the new frontend is working properly. While I'm working on that I am coming a cross multiple instances where the API doesn't handle errors properly. I will track the instances in this ticket.
So far:
Internal Server Error when accessing visualiser that isn't available should be a 404 instead
Internal Server Error when accessing image that isn't available should be a 404 instead
OK (200) when doing something wrong during upload should be an error (multiple cases?)
The API should have consistent and proper usage of HTTP error codes.
Right now wrong usage mostly results in an Internal Server Error (50x) and doesn't properly tell the user what went wrong. Furthermore, the API sometimes doesn't respond with an error code at all when obviously user input wasn't okay (see uploading files).
See https://httpstatuses.com for a list of responses.
The text was updated successfully, but these errors were encountered: