-
Hi.
Thank you for ProblemDetails.WebApi.
I noticed the property name values in the `JsonProperty` attributes decorated on the properties in the `ProblemDetails` class are lowercase.
This isn'…
-
-
While create a PR for #83, I noted that all the error responses in the spec that carry `ErrorInfo` schema in the body should have the content type set to `application/problem+json` instead of `applica…
-
Some of the requirements and recommendations in section 3.1 conflict with the spirit of RFC 7807, which it references.
There is presently a requirement that:
> The "instance" value MUST be the e…
-
# Describe
- Compare 1.20 file and object changes
- `ServeMux` reimplemented, moved from `server.go` to file `servemux.go`.
- The `Request` object has a new attribute `PathValues []string` an…
-
While testing new certificates I encountered that if I receive this response:
```xml
401
Unauthorized
https://tools.ietf.org/html/rfc7235#section-3.1
00-0000000000000000-0000000000-00
…
-
While replacing a custom implementation of Problem Details by the new one that came with Spring 6 I was puzzled by how content negotiation is implemented. I'm currently using Spring Boot 3.0.0 with Sp…
-
In the different WGs we have 2 approaches to specify the schema for error responses:
1) Reference to the common `ErrorInfo` model:
```
components:
schemas:
ErrorInfo:
type: objec…
-
I don't know wether this is the right place to ask this (so sorry if it's not):
What is your take on Spring 6 wich has support for RFC 7808?
Will there be support for Spring 6 (and will you inte…
-
The errors from our Fastify APIs are generated in RFC 7807 format.
https://www.rfc-editor.org/rfc/rfc7807
It would be good to have an ErrorDisplay component that could take one of these data str…