Pass CSRF token directly as configuration, don't rely on presence of cookie or hidden input #15
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
16 tasks
Bypassing need to check for token in cookie or input.
|
@nijel while reviewing this PR the thought occurred to me: why don't we pass the token directly as configuration? Avoids the need to go looking for it in different places and it assures the token is always available. What do you think? I've pushed a commit to your branch that implements this. |
|
Great idea. That avoids dependency on the Django configuration and page content. |
Stormheg
changed the title
Stormheg
added a commit
that referenced
this pull request
Aug 2, 2024
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 works if I manually modify JavaScript, but I have no knowledge of typescript, so there might be something missing.
Fixes #14