-
The goal for this issue is to add a representation for an RFC 7807 problem detail, and integrate it into Spring MVC and Spring WebFlux error response handling.
On the WebFlux side we have the `Resp…
-
Hello,
When sending a request ending in error, with an `Accept` header set to `*/*`, the response is sent with `Content-Type` set to `text/plain`. Shouldn't it be `application/json`?
Example:
…
-
I'm trying to make a custom rule based on the *unkown-error-format* that can be found here [here][1]. Using this Open API document as an example:
*openapi-generated.yaml*
````yaml
openapi: 3.0.3
…
-
### Describe the bug
Utilizing the `error` helper documented here: https://kit.svelte.dev/docs/load#errors
When I use `throw error(400)` in a server file, its respective page redirects to an error…
-
_Comment by @fpalombini_
[Section 2](https://www.ietf.org/archive/id/draft-ietf-core-problem-details-04.html#section-2):
> ~~~
A short, human-readable summary of the problem shape. It SHOULD
NOT…
-
The HTTPAPI WG has very recently adopted the rfc7807bis document. We should monitor what happens there and make sure we any "lesson learned" in the HTTP world is picked up and digested.
More cont…
-
## Background and Motivation
At the moment, all properties ProblemDetails have attribute JsonPropertyNameAttribute with camelCase-style.
[ProblemDetails](https://github.com/dotnet/aspnetcore/blo…
-
Do what the title says in the manager's session creation routines, with sensible error messages.
-
Once #28187 provides `ProblemDetail` along with the `ErrorResponse` hierarchy of exceptions that encapsulate HTTP status, headers, and body, to support RFC 7807, it is also necessary to improve conte…
-
Relate to #282. We have code as a key supported with #295 but still need a generic key value.
Some more features:
- Move the knowledge to the model, so that we do not need to check annotations i…