-
This would be helpful to facilitate customization of error messages for all framework exceptions especially for RFC 7807 problem details, under #27052.
-
I currently have several endpoints that can return possible errors/non-200 status codes. When these errors occur, the response `Content-Type` header is set to `application/problem+json` per [RFC 7807]…
-
### 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.
So when I was browsing my API using…
-
_Comment by @fpalombini_
[Section 5.2](https://www.ietf.org/archive/id/draft-ietf-core-problem-details-04.html#section-5.2):
> ~~~
+=======+=============+===========================+===========+
…
-
### The act. state
In the Joomla-backend, there are much ways to filter the listview. Some are selectable by various dropdown-fields, others could be filtered by some keys written direct to the sea…
-
Keep it consistent with RFC title [Problem Details for HTTP APIs](https://www.rfc-editor.org/rfc/rfc7807)
-
-
### Issue Description
Right now, Echo makes it easy to write handlers that return JSON - that is, `application/json` - documents. However, it doesn't make it as easy as it could to write handlers t…
-
**[Ammar Husain](https://jira.spring.io/secure/ViewProfile.jspa?name=ammarhusain007)** opened **[SPR-16318](https://jira.spring.io/browse/SPR-16318?redirect=false)** and commented
For a vanilla REST …
-
**What is a problem?**
I have some API schemas that use less-obvious (valid) OpenAPI constructs that are not supported by this library because of the hardcoded strictness in the `openapi_parser.enu…