Replace HttpException with BadRequestHttpException in CSRF validation #8272
+1
−1
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.
Substitute HttpException with BadRequestHttpException to more accurately indicate a bad request (HTTP 400) error during CSRF token validation.
Subject
This PR refactors the CSRF token validation in the
validateCsrfToken
method by replacingHttpException
withBadRequestHttpException
. This change improves clarity by accurately indicating an HTTP 400 error when an invalid CSRF token is detected.I am targeting this branch because the change is backward compatible and addresses an improvement in error semantics without breaking any existing functionality.
Changelog