We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Error messages (ie: 400: Bad Request) should contain messages describing what caused the error (except for sensitive information).
400: Bad Request
For example, when the client sends an invalid JSON doc, the server should return an error payload like so:
{ "code": 400, "name": "Bad Request", "description": "The browser (or proxy) sent an invalid JSON document." }
The server should also detail what field caused a validation error to occur (ie: sending fields of the incorrect datatype)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Error messages (ie:
400: Bad Request
) should contain messages describing what caused the error (except for sensitive information).For example, when the client sends an invalid JSON doc, the server should return an error payload like so:
The server should also detail what field caused a validation error to occur (ie: sending fields of the incorrect datatype)
The text was updated successfully, but these errors were encountered: