-
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…
-
This issue is to summarize the discussions and progress of #396, which sought to develop a standard output format for JSON Schema.
This issue does **not** cover standardized error message wording. …
-
Just a random thought I had now while setting up status code logging for a few APIs: It would be awesome if the problem detail properties from RFC 7807 could be expressed in a `Link` header with an ap…
-
So as is, the PURL specification's use of URIs has some issues standing in the way of adoption by the wider Internet community:
- Multiple schemes that are part of a broader interconnected protocol…
-
I'm not sure if it is caused by the URN or the `prefix = ""` nervertheless it is a bug.
The generated file is missing it's filename and only has the `.xsd` extension. Furthermore the namespace iden…
-
I've just found out that the `SerializableError` class is derives from `Dictionary` but technically used as `Dictionary` [link](https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNetCore.Mvc.Core…