Handle AntiforgeryValidationException in CookieOnlyAutoValidateAntiforgeryTokenAuthorizationFilter#1152
Merged
hishamco merged 1 commit intoJun 8, 2026
Conversation
|
Member
|
I will review ASAP then merge |
hishamco
approved these changes
Jun 8, 2026
Member
|
Thanks |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This is a follow-up to #1150.
antiforgery.ValidateRequestAsync()throwsAntiforgeryValidationExceptionwhen the CSRF token is missing or invalid. Because the exception is not caught, it propagates as an unhandled exception and produces a 500 Internal Server Error instead of the expected 400 Bad Request.This PR wraps the call in a
try/catchand setscontext.Result = new AntiforgeryValidationFailedResult().