-
* Unify error handling on SDK
* Keep format with manager API return
-
Hi,
I am using certbot to test a non-Letsencrypt server implementation.
Platform is Ubuntu 18.04, installation was done out of ppa:certbot/certbot repo.
Certificate enrollment and revocation…
-
Remove: `When this member is not present, its value is assumed to be ["about:blank"](about:blank).`
Rationale: This would **require** (!) conforming clients to lump all non-typed errors together in…
-
In https://github.com/w3c/vc-data-integrity/issues/66#issuecomment-1300669373, @mprorock wrote:
> should we consider using [RFC 7807](https://www.rfc-editor.org/rfc/rfc7807) for error responses?
T…
-
how can i disable stackTrace response in production ?
-
Problem Details is an internet standard - https://www.rfc-editor.org/rfc/rfc7807
In ASP.NET Core, `ProblemDetails` is serialized with `IProblemDetailsWriter`. The default implementation is `Default…
-
### Problem
Currently when we call `api/v1/contracts/call` under the web3 module and there is a failure in the execution, we return only the error code in the message field of the JSON error respon…
-
Hi, I think this may be related, but the casing for ProblemDetails is also inconsistent. ProblemDetails itself defaults to camel case, but as you can see above when describing the "Summary" field, it'…
-
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
- Construct a new Quarkus project with the steps indicated in the proje…
-
### Improve and allow a more consistent error handling
Hi,
The error handling in kong is somewhat inconsistent:
- If the error come from nginx and is catched by the directive defined in the [n…