Improve CSRF Documentation #584
Open
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
This update extends the documentation regarding CSRF protection in the library. Specifically, it provides additional insights into the 'csrf' input name configuration for Non-FlaskForms in preventing the common "CSRF token not found error." Users can now better understand the implication of the WTF_CSRF_FIELD_NAME config. Additionally, a new example has been included in the JavaScript section that demonstrates how to send the 'csrf_token' as a Jinja2 variable (to the backend) with the Fetch API using a Vanilla JavaScript example. This example shows the proper implementation of CSRF protection when working with the Fetch API, contributing to a more secure application.
for more information, see https://pre-commit.ci
Add extra space after markup.
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.
This update extends the documentation regarding CSRF protection in the library. Specifically, it provides additional insights into the 'csrf' input name configuration for Non-FlaskForms in preventing the common "CSRF token is missing." Users can now better understand the implication of the
WTF_CSRF_FIELD_NAMEconfig.Additionally, a new example has been included in the JavaScript section that demonstrates how to send the 'csrf_token' as a Jinja2 variable (to the backend) with the Fetch API using a Vanilla JavaScript example. This example shows the proper implementation of CSRF protection when working with the Fetch API.