-
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
-
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…
-
According https://tools.ietf.org/html/rfc7807#section-6.1 there will be more correct to set Content-Type header to `application/problem+json` when using `flatten_exception_format: 'rfc7807'`.
-
I wanted to check and see if people would be open to switching the error code returned as part of the spec to a string instead of an integer. So things would like like this:
```
{
code: 'ITEM_N…
obo20 updated
4 years ago
-
### Is your feature request related to a problem? Please describe.
I use aspnet core 3.0, and I am generating the client using openapi-generator for Elm. The problem is that Elm is a typed programm…
-
Similar to https://github.com/solid/specification/issues/28
-
**Do you want to request a *feature* or report a *bug*?**
feature
**What is the current behavior?**
Errors returned from the gateway are not in a standards based format
**What is the expec…
-
There is a RFC 7807 for a response structure for error cases. For more details see https://tools.ietf.org/html/rfc7807.
For a form validation error it could be like this:
```
{
"type": "http…
-
Change Problem Details according to @sm-g comment:
@kgrzybek I'm reading your https://www.kamilgrzybek.com/design/rest-api-data-validation/ and found that `title` in problem details reponse which y…
-
In GitLab by @Brend-Smits on Apr 19, 2020, 13:21
How should we let the frontend know what went wrong? Normally I create new headers and add those to the request if something went wrong for whatever r…