-
Notifications
You must be signed in to change notification settings - Fork 38.2k
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
Handle DataBufferLimitException as HTTP 413 responses #32558
Handle DataBufferLimitException as HTTP 413 responses #32558
Conversation
@mysend12 Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
@mysend12 Thank you for signing the Contributor License Agreement! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
spring-web/src/main/java/org/springframework/web/server/ServerWebInputTooLargeException.java
Outdated
Show resolved
Hide resolved
This comment was marked as resolved.
This comment was marked as resolved.
79e39c7
to
3ca0ba9
Compare
…t in 413 instead of 500
3ca0ba9
to
0b57b6c
Compare
@injae-kim thanks for trying to help but please refrain from providing guidelines to contributors. The first one is actually wrong, we do not need a reference to the original issue in the commit message. |
oh sorry, I got it! actually PR author @mysend12 is my friend and I'm helping him to contribute(by pair programming!) so provide guideline by comment :) I'll don't do this~! 🙇 thank you! |
Thanks for your contribution @mysend12 , this is now merged in main and will be shipped with the next 6.2 milestone. |
origin issue: #32113
hello. In WebFlux, when a DataBufferLimitException occurs because the payload is larger than the setting value (spring.codec.max-in-memory-size), a 413 Too Large Body status code should be returned, but a 500 status code was returned, so that part has been corrected.