-
The API should return more descriptive errors, rather than just plain status code errors, such that the frontend can display this information in a more user friendly (and descriptive) manner.
A sug…
-
**Expected Behavior**
when this is used:
```java
@Bean
SecurityFilterChain configure(HttpSecurity http, AuthorizationManager authz)
throws Exception {
http.oauth2Resour…
-
Time is short so don't do this now but I suggest reaching out to Justin Richer about HTTP signatures to see if they might benefit from some problem types too. See https://httpwg.org/specs/rfc9421.html…
-
https://www.rfc-editor.org/rfc/rfc7807
-
https://datatracker.ietf.org/doc/html/rfc7807
-
For proper error response
https://datatracker.ietf.org/doc/html/rfc7807
-
The problem RFC explicitly states in https://www.rfc-editor.org/rfc/rfc9457.html#section-3.1.4:
> Consumers SHOULD NOT parse the "detail" member for information; extensions are more suitable and le…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Is your feature request related to a problem? Please describe the problem.
This issue is not related to a prob…
-
404 is one we do mandate, and we sometimes say it must be a 400, but most of the time we just say "an error must be generated". Do we need to be more precise? Should we standardize the error messages…
-
Hilla already provides some [error-handling mechanisms](https://hilla.dev/docs/react/guides/endpoints#error-handling) to catch errors occurring in the backend. However, for many use cases, having a gl…