-
Notifications
You must be signed in to change notification settings - Fork 37.7k
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
DataBufferLimitException in WebFlux controllers should result in 413 instead of 500 #32113
Comments
Few more thoughts: the error handler probably shouldn't map Also, I do not know if this happens in WebMVC all well; that is a 500 instead of a 413, but it should be straightforward to validate. |
DataBufferLimitException
in WebFlux controllers should result in 413 instead of 500
DataBufferLimitException
in WebFlux controllers should result in 413 instead of 500…t in 413 instead of 500
Closing in favor of PR #32558 |
When using Spring WebFlux, there is a maximum limit on the payload size, defined by
spring.codec.max-in-memory-size
(default value is 256KB). If a request is made with a body exceeding this size,DataBufferLimitException
is thrown. The default error handler then returns a500 Internal Server Error
response. This is actually not a server side error, but instead a server side validation. This should result in413 Content Too Large
instead.Spring Boot version: 3.2.1
The text was updated successfully, but these errors were encountered: