-
We don't have a standard format for error responses for GET or POST requests.
[RFC 7807](https://datatracker.ietf.org/doc/html/rfc7807) provides a standard JSON format for errors, including machine…
evanp updated
1 month ago
-
### Description
Readability and conciseness of errors via the HTTP API (`agent_api_rest`) can be improved when following the [Problem Details for HTTP APIs (RFC 7807)](https://datatracker.ietf.org/…
-
Currently the attributes 'title' and 'status' in the CommonErrorResponse object are all optional although the [RFC 7807](https://datatracker.ietf.org/doc/html/rfc7807) identifies these as required.
…
-
Hi @edaniszewski ,
first of all thanks for providing that package to the community. I just reviewed your package because we think about using it in our software development operation: this is very we…
-
With Spring Framework 6.0 providing first-class support for RFC-7807 (see https://github.com/spring-projects/spring-framework/issues/27052), Spring HATEOAS should probably deprecate its own RFC-7807 s…
-
### 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
1 month ago
-
[RFC 7807 Problem Details for HTTP APIs](https://datatracker.ietf.org/doc/html/rfc7807) defines a standard error response format for HTTP APIs. The TypeSpec HTTP library should include a model that de…
-
For proper error response
https://datatracker.ietf.org/doc/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…
-
Follow [RFC 7807](https://tools.ietf.org/html/rfc7807) as error response format