Affects: 5.3.9
HTTP requests with malformed form url encoded data result in HTTP 500, not 400. I observed that in a WebFlux application when form data is mapped into my object using built-in mapping or when accessed via ServerWebExchange.formData
. Exception is raised in FormHttpMessageReader and maps to HTTP 500. It should be 4xx error as the input is malformed
Example HTTP requests body causing problems:
username=test%%%invalid
Comment From: snicoll
Can you please share a small sample we can run ourselves to reproduce what you've described?
Comment From: spring-projects-issues
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Comment From: spring-projects-issues
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.