-
Is there any plan for support of RFC 7807: Problem Details for HTTP APIs
https://tools.ietf.org/html/rfc7807
Or is there any guidance around sample implementation?
-
This is a project to begin defining a set of objects to be returned as part of error codes, providing a structure, and common language set to describe common, as well as custom error responses.
-
The [acme protocol](https://tools.ietf.org/html/draft-ietf-acme-acme-17) returns in https://tools.ietf.org/html/draft-ietf-acme-acme-17#section-7.1.3 an error object which is in the format of RFC 7807…
-
Some colleagues of mine are looking into the problem library for our spring boot app. One discussion has come up about the inclusion of the status code in the body, since it is already provided in the…
-
Default error response provider should return errors in **ProblemDetails** format in compliance with [RFC 7807](https://tools.ietf.org/html/rfc7807).
ASP.NET Core has first-class support for Proble…
-
I already had this question on the mailing list probably years ago. I am curious if there is any progress/recommendation about this.
When multiple persons are working on the same resource there can…
ghost updated
3 years ago
-
Allowing the application to set the response reason string has been deprecated. Jetty-10 should change so that the message passed to sendError is only used in the error page body and not as the reaso…
gregw updated
3 years ago
-
Apply [API guidelines](https://github.com/microsoft/api-guidelines) as per CPR feedback across all relevant repositories.
Next steps:
- [x] Write & review json code
- [x] Update in lang repos
…
-
No that I know about the API 😜 ...
The Screenshot says "x-api-key" but it has to be "X-Api-Key". Did not work with lowercase
![Bildschirmfoto 2020-10-05 um 10 04 08](https://user-images.githubuse…
-
Hi there 😃
I was interested in introducing this library on the current project I work for.
After some digging on others issues, there might be a gap between what this library is for and what I wa…