-
RFC 9457 (https://www.rfc-editor.org/rfc/rfc9457.html) defines a Problem Details response for HTTP APIs.
It proposes a standard response object to explicit the error (instead of just returning erro…
-
## 現状と課題
入力値検証で例外が発生し、`400 Bad Request`を返す場合、その`message`を`INFO`レベルで記録しているが、
レスポンスボディは空にしている。
受け取った側が分かりやすいように、エラーの概要をメッセージボディで返したい。
なお、単純に例外の`message`を返すだけだと、`MethodArgumentNotValidException`と…
-
In the swagger API documentation file (OSDM-online-api-v3.0.3.yml) is there a reference to RFC 7807. Should this be replaced with reference to [RFC 9457: Problem Details for HTTP APIs](https://datatr…
-
Opened by @aphillips via IRC channel #i18n on irc.w3.org
Due: 2024-04-04 (Thursday 4 April)
-
The current specifications, while complying, does not directly follow the standard as they need a URI, among other stuff. See [Defining New Problem Types](https://www.rfc-editor.org/rfc/rfc9457.html#n…
-
RFC 7807 is deprecated in favor of RFC 9457.
https://www.rfc-editor.org/rfc/rfc9457.html
https://blog.frankel.ch/problem-details-http-apis/
-
### Description
As a developer I would like to configure the framework to display the `message` of chosen `Exception`s in the `Response`.
The status code and log level configuration per `Exception…
-
Hello, I have a single go program which provides two separate `huma.API`s. For one API, I'd like to keep the RFC9457 error responses which are used by default, but for the other API I need to use a cu…
-
https://www.rfc-editor.org/rfc/rfc9457.html
`title` and `detail` would give more specifics than the current way its being handled
-