-
### What is the question?
Is there any reasonable way of transforming the `exception.message` of an exception record? I have this `ProblemDetails` (RFC 7807) exception that carries its information in…
lvde0 updated
2 months ago
-
I'm noticing that some endpoints are returning errors in the 'problem details' format. Review the rest of the endpoints to ensure consistency, and where it makes sense, implement the 'details' part o…
-
Support extension members as well.
See also: https://tools.ietf.org/html/rfc7807
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Is your feature request related to a problem? Please describe the problem.
This issue is not related to a prob…
-
https://datatracker.ietf.org/doc/draft-ietf-httpapi-rfc7807bis/ is a brand new standard.
Since I need a neat, predictable format for my JSON errors, maybe I should use this one?
-
Hi,
I was interested into integrating the error format as the RFC specification 7807 that basically is a standard format to return errors on an REST API. If you find it interesting we could have a …
-
At present, the default error object returned from an invalid request is of the format:
```
HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json
{
"error": "field1: error1; fi…
-
When calling Vaadin Service methods, Connect validates the parameters passed to the server-side (based on the [JSR-380](https://beanvalidation.org/2.0/) spec. If validation fails the error details are…
-
-
[RFC-7807](https://www.rfc-editor.org/rfc/rfc7807) is a popular standard for HTTP API error response bodies. Both the [`problemdetails`](https://docs.rs/problemdetails/latest/problemdetails/) and [`ht…