-
## Problem / Motivation
- WHO wants this? Developers and product managers
- WHEN and WHERE do they want it? Available on a public URL accessible from any browser
- WHAT do they want? Some conten…
-
What about adding support for [RFC7807 "Problem Details"](https://tools.ietf.org/html/rfc7807), which is a spec for standardized error responses in JSON format?
Or is that an issue for the php-json…
-
* [ ] Add a filter
* [ ] Include correlation id if available
* [ ] Ensure analyzer works (#8288)
--------
* RFC 7807
* Use ProblemDescription as the preferred format for "error" responses from …
-
I love your ideas with the new health check middleware. I typically have something homemade brewed into all API's and websites I'm creating. My health checks (`/isalive` in most instances) are pinged …
-
After adding support for RFC 7807 error responses to Cyrus JMAP, it looks like we may want additional codes to indicate that the request exceeds a server limit (e.g. maxSizeRequest) and that a creatio…
-
Our REST responses in error situations should follow [RFC 7807](https://tools.ietf.org/html/rfc7807). Some concrete guidance can be found in the [Zalando RESTful API guidelines](https://zalando.github…
-
Report problems from Facility APIs in a format described by [RFC 7807](https://tools.ietf.org/html/rfc7807). It's OK if this requires [ASP.NET Core 2.1](https://blogs.msdn.microsoft.com/webdev/2018/02…
-
Some of the services uses a GlobalExceptionFilter that returns a internal server error object.
There is currently no Swagger Operation decorator that adds Http Status Code 500 as a valid response.
T…
-
Hi,
In the spec, the recommended transport is RESTful APIs.
Any implementation will need to signal errors. Does it make sense for the CPIX spec to specify the response body contract for errors?
…
-
Core 2.1 planning suggestion/contribution
So I watched the ASP.NET Community Standup (July 11th, 2017) [YouTube video](https://youtu.be/pNsilbW2x0I?t=35m40s) a while ago and saw @DamianEdwards talk a…