-
This issue is about how to identify Problems – which is neccessary for correct handling in client implementations (e.g. when a payment fails beacuase of insufficient funds etc).
I'm posting this as…
-
## Checklist
- [ ] I have verified that that issue exists against the `master` branch of Django REST framework.
- [x] I have searched for similar issues in both open and closed tickets and cannot …
agowa updated
3 years ago
-
## Headline
Create an error mapping with message and codes for the API response
### Why we need it?
- Easier 3trd-party integrations;
- Better error handling;
- Improve the documentation;
…
-
**Is your feature request related to RFC7807? Please describe.**
Quarkus provides custom exception mapper for this exception, and client gets 'test/html' response:
`org.jboss.resteasy.plugins.provid…
-
*Title*: *: Include an additional header and problem details in the message body of the response for overload scenarios*
*Description*:
We know that _x-envoy-overloaded_ header is set on the downs…
-
Which can handle error message format and logging.
See https://echo.labstack.com/guide/error-handling
-
How do you guys handle decisions based on ProblemDetails between the API layer and Frontend?
status, type, detail, instance
I.e.,
1. ChildService calls MotherService -> "Can I have IceCream?"
…
-
Good default formats for exceptions is [rfc7807]. A JSON-representation of an error is formulated like the following object:
{
"type": "URI: https://content.omgevingswet.overheid.nl/id/[/{categori…
-
We do not use these Problem members as of today (unless client throws ThrowableProblem with those fields provided), but they are a vital part of the standard:
https://tools.ietf.org/html/rfc7807#page…
-
It's currently rather difficult to add support in a general fashion for adding opentracing span/trace information (considering the `instance` member seems a ready fit for the info).
## Detailed Des…