This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
Return BadRequest response when antiforgery token validation fails #3884
Conversation
This file contains 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
| static ValidateAntiforgeryTokenAuthorizationFilterLoggerExtensions() | ||
| { | ||
| _antiforgeryTokenInvalid = LoggerMessage.Define<string>( | ||
| LogLevel.Error, |
There was a problem hiding this comment.
Not sure if this should be Error.
There was a problem hiding this comment.
Info IMO. I think that's the level we use for authentication failures.
|
Tests? I'd really expect this to impact existing functional tests. If we don't have unit test coverage, then add it. ⌚ |
|
🆙 📅 |
|
|
ajaybhargavb
force-pushed
the
antiforgery-badrequest
branch
from
21659fa to
bf1fcf6
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 - aspnet/Antiforgery#28
@pranavkm @rynowak