-
Notifications
You must be signed in to change notification settings - Fork 308
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.
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 Response like RFC 7807 #1445
Comments
@pratik-k-ev can you please elaborate your issue. Want to know more about the problem you are facing and how we can help to resolve it |
The current error response format is {
"error": {
"message": "..."
}
} I wanted to extend error response fields and standardize according to RFC 7807. Fields in RFC 7807 {
"type": "string",
"title": "string",
"status": "integer",
"detail": "string",
"instance": "string",
"extensions": {
"field_name": "value"
}
} Is there way to follow this, or extend current error response fields? |
@Umang01-hash , Please assign this issue to me ..... |
Hey @pratik-k-ev, the error approach is proposed and I can see it has also become obsolete being replaced by RFC 9457. We might extend support to send such errors through custom errors, however can you please let me know if this is still under proposal or has been accepted ? Based on that, we can work on this feature for your usecase. |
Is there a way to customise error payload fields..? |
Is your feature request related to a problem? Please describe.
I want to return response with much more detail.
Describe the solution you'd like
According to RFC 7807, can update the error response to support those fields.
Describe alternatives you've considered
Not sure, maybe error customize the error response payload.
The text was updated successfully, but these errors were encountered: