Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Problem Details for HTTP APIs (RFC 9457) for api errors #495

Open
johnksv opened this issue Sep 17, 2024 · 2 comments
Open

Implement Problem Details for HTTP APIs (RFC 9457) for api errors #495

johnksv opened this issue Sep 17, 2024 · 2 comments

Comments

@johnksv
Copy link
Contributor

johnksv commented Sep 17, 2024

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 suggestion is to implement the well known RFC 9457 standard for this, as documented here: https://datatracker.ietf.org/doc/html/rfc9457
Spring (and other frameworks) also has out-of-the-box support for this, e.g.: https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-ann-rest-exceptions.html

As discussed in community meeting in August.

@trygu
Copy link
Contributor

trygu commented Sep 20, 2024

This one, I think is quite important. Especially when more people in our office create services, and we have policy systems like Kyverno installed. It can be a bit time consuming to debug errors. So I vote for this.

@olevitt
Copy link
Contributor

olevitt commented Sep 27, 2024

I started work on this in #504.
Feel free to give feedback or contribute to this.
My understanding of this is that the current state of the PR already handles generic exceptions. For more details we should create and throw corresponding exceptions in the controllers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants