-
There's an internet standard to model to carry machine-readable details of errors
https://datatracker.ietf.org/doc/html/rfc7807
The proposal is to use "Problem" instead of "ErrorMessage". Thi…
-
Should we define a header that can carry problem details?
E.g., for the first example in the spec:
~~~ json
{
"type": "https://example.com/probs/out-of-credit",
"title": "You do not have e…
-
the examples of errors use a pattern of using a `describedby` link in a `Link` header, and then (supposedly) using a human-readable error message. what about using RFC 7807 instead and using examples …
-
# What is currently missing?
Usage of LinkedHashMap in connector calls can be replaced with HashMap ?
Review usage of synchronized
Exception handling in clusterapi
# How could this be improved…
-
Example added for multiple problems shows use of an extension called `property_location` which is a JSON Pointer RFC6901 that points to the source of the problem in the corresponding HTTP request. Suc…
-
The 404 handler generates an RFC 7807 `application/problem+json`, but it doesn't point to a valid schema. Here is a sample 404 response:
```json
{"$schema":"http://localhost:8888/ErrorModel.json"…
-
**Describe the bug**
In an application (using Spring Boot 3.0.1) the response body does not match the `Content-Type` header for a 403 Forbidden response if the request contains the header `Accept…
-
Please report 3.2 issues here:
```
composer config minimum-stability beta
composer update api-platform/core
composer recipes:update
```
-
We have a schema for the error but the microservices are not implementing it. This schema was derived from [RFC 7807](https://blog.restcase.com/rest-api-error-handling-problem-details-response/).
S…
-
This has been requested a number of times but so far has been deferred to Spring Boot which supports error response details. The corresponding https://github.com/spring-projects/spring-boot/issues/195…