-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[Security] Tell about stateless CSRF protection #20964
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 7.2
Are you sure you want to change the base?
Conversation
a9af992
to
3b50c2b
Compare
@@ -1164,7 +1198,8 @@ settings is configured. | |||
|
|||
For more details, see :doc:`/forms`. | |||
|
|||
.. _reference-form-field-name: | |||
csrf_protection | |||
''''''''''''''' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This header starting a section with no content looks wrong to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's currently missing, eg field_name is under csrf_protection
this declares one more nesting level
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest keeping the markers consistent in the file then, by using .
as the marker below ~
and another marker for the lower level (i.e. using .
here and changing the marker of field_name
and of your 2 new settings). It will reduce the risk of breaking the structure with future changes
Fix #20306