Use a TagHelperInitializer to set the Antiforgery attribute #840
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
gunndabad
force-pushed
the
antiforgery-initializer
branch
from
0bfec26 to
0922a5a
Compare
hortha
approved these changes
Sep 29, 2023
gunndabad
force-pushed
the
antiforgery-initializer
branch
from
0922a5a to
a7098e7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We have been using a mix of
action+asp-antiforgery=trueandtrs-actionfor generating form tags with an anti-forgery attribute. This adds aTagHelperInitializerthat defaultsAntiforgerytotrueand removes the now-redundantTrsActionTagHelper.