Delay assignment of csrftoken in Graphiql #1289
Merged
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
csrftoken
is currently assigned only whengraphiql.js
is first loaded.The current
csrftoken
can rotated by Django, for instance when a user logs in. rotate_token performs the rotation.When this happens, the
csrftoken
held bygraphiql.js
is invalid and Graphiql will receive CSRF errors.This PR delays the assignment of the
csrftoken
by moving it into thehttpClient
function so when thecsrftoken
is rotated by Django, Graphiql can pick up the new token from the cookies.