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
Report invalid @MultipartForm format #26158
Labels
Milestone
Comments
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Jun 16, 2022
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Jun 16, 2022
…lization Relates to: quarkusio#26158
Thanks for reporting. #26170 takes care of it |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Jun 17, 2022
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Jun 17, 2022
…lization Relates to: quarkusio#26158
/cc @FroMage, @geoand, @stuartwdouglas |
geoand
added a commit
that referenced
this issue
Jun 17, 2022
Improve server side multipart exception handling
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In case a
multipart/form-data
request is handled, for example:With a DTO:
If the
format
is provided correctly, it works as expected, otherwise it fails silently with a 500 - whether the JSON is wrongly formatted or the elements do not respect theMyEnum
values. But in this case I want to be able to notify the user that the request is wrong, returning a custom message - or at least being able to see in the logs why the request failed.Implementation ideas
No response
The text was updated successfully, but these errors were encountered: