-
Following #3 and #9 we propose to implement [RFC7807](https://tools.ietf.org/html/rfc7807) to standardize API error handling. More specifically, define "Title", "Status", and "detail" [members](https:…
-
According to **RFC-7807** (see https://tools.ietf.org/html/rfc7807) it would be useful to provide an `invalid-params` field in case of `400 Bad Request` errors. This field is supposed to contain ALL v…
-
## Detailed Description
To complement the Problem mapping capability of `SecurityProblemSupport`, a custom `AuthenticationFailureHandler` should be added to ensure exceptions in the security filter…
-
The spec currently encourages but doesn't force the use of a reverse-DNS name for the [event type](https://github.com/cloudevents/spec/blob/v1.0.1/spec.md#type) and the examples only use dot notation.…
-
Recommend that aspnetcore api error handling be enhanced to align with RFC7807. Details of specific errors passed back to clients in json format. https://tools.ietf.org/rfc/rfc7807.txt
There are…
-
Hello !
I took a little time to check what https://github.com/symfony/symfony/issues/43021 involve for this bundle. And the only blocker is https://github.com/FriendsOfSymfony/FOSRestBundle/blob/3.…
-
Capturing @ioggstream's response from email thread with follow up questions. Should Problem Details JSON Object schema have any member indicating that the problem(s) is an error(s) or warning(s)? If y…
-
In DIDCommV1 we defined a semi-standard format for error reporting in [RFC 0035](https://github.com/hyperledger/aries-rfcs/tree/master/features/0035-report-problem). I think having a standard format w…
-
## I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support r…
-
> This issue will be updated as time goes on to reflect the current state of this work
Currently Gleam provides a `Result` type that represens success or failure, but no generic error type. Gleam u…