Fix wrong exception handling for boolean @RequestParam #36066
Closed
+41
−9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spring-projects-issues
added
the
status: waiting-for-triage
Signed-off-by: Aman Gautam <amangautam2128@gmail.com>
Gautam-aman
force-pushed
the
fix/boolean-requestparam-bad-request
branch
from
ba4d0e3 to
a5e781f
Compare
Member
|
See #36061 (comment) |
bclozel
added
status: declined
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Invalid boolean values supplied to
@RequestParamcould result inIllegalArgumentExceptionescaping argument resolution, leading toinconsistent error handling.
Changes
IllegalArgumentExceptionduring argument conversionMethodArgumentTypeMismatchExceptionRequestMappingHandlerAdapterTestsResult
Boolean request parameter conversion errors are now handled consistently
with other type mismatches.