-
### Version
None
### Is your feature request related to a problem? Please describe.
_No response_
### Describe the solution you'd like
Currently we are using RFC7807 https://www.rfc-editor.org/…
-
Since you seem to serialize the error as JSON , please take a look at RFC7807 for standardizing JSON errors. https://paul.totterman.name/posts/rfc7807/
-
https://datatracker.ietf.org/doc/html/rfc7807
-
### Prerequisites
- [X] I have written a descriptive issue title
- [X] I have searched existing issues to ensure the feature has not already been requested
### 🚀 Feature Proposal
We could …
-
See https://www.rfc-editor.org/rfc/rfc7807 or https://datatracker.ietf.org/doc/html/rfc7807
-
https://www.rfc-editor.org/rfc/rfc7807
-
https://tools.ietf.org/html/rfc7807 appears to be super useful for most JSON/XML APIs, so we should support it.
-
It appears don will fallback to a 500 error and uses a simple format `{ "message": "Internal Server Error" }`
It would be nice if it used a standard response format with a method of hooking in vali…
-
**Expected Behavior**
There should be an option to enable RFC7807-style ProblemDetail-responses when using Spring Security 6.
**Current Behavior**
There is currently no option to enable this…
-
The default error handling of FastAPI is a bit weird. You get response bodies such as
```
{"detail":
[
{"loc": ["body", "title"], "msg": "field required", "type": "value_error.missing…