-
## Background and Motivation
At the moment, all properties ProblemDetails have attribute JsonPropertyNameAttribute with camelCase-style.
[ProblemDetails](https://github.com/dotnet/aspnetcore/blo…
-
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…
-
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…
-
Do what the title says in the manager's session creation routines, with sensible error messages.
-
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…
-
### Prerequisites
- [X] I have written a descriptive issue title
- [X] I have searched existing issues to ensure the bug has not already been reported
### Fastify version
3.28.0
### Plugin versio…
-
Olá,
Estamos recebendo erro 500 ao tentar criar um relato de infração com o tipo REFUND_CANCELLED informando o EndToEnd da devolução no atributo TransactionId.
```xml
https://dict.pi.rsfn…
-
## I expect
The default 429 message to be a problem+json RFC 7807 message
with an error payload.
## instead
I
See message: "Too many requests, please try again later.",
-
How should a Thing Description define error conditions for form requests? How does a client know what different success and failure responses are possible to a given form request and what they mean?
-
### Expected Behavior
When `HttpResponse` is returned from an `ExceptionHandler` with a non-200 status code and custom headers I expect the `MicronautAwsProxyResponse` that is returned to AWS API G…