Fix CSRF when CSRF_USE_SESSIONS is enabled #619
Merged
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
The front-end currently checks for the `input[name="csrfmiddlewaretoken"]` element if `CSRF_COOKIE_HTTPONLY` is set, but according to the [Django docs], it should do the same thing if `CSRF_USE_SESSIONS` is set, as it will also mean the token is not available in a cookie. [Django docs]: https://docs.djangoproject.com/en/5.0/howto/csrf/#acquiring-the-token-if-csrf-use-sessions-or-csrf-cookie-httponly-is-true
|
Thanks! I will get it reviewed and merged into the next release. |
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.
The front-end currently checks for the
input[name="csrfmiddlewaretoken"]element ifCSRF_COOKIE_HTTPONLYis set, but according to the Django docs, it should do the same thing ifCSRF_USE_SESSIONSis set, as it will also mean the token is not available in a cookie.