Solved Cookie token creation for requests#549
Open
stijnpotters1 wants to merge 3 commits into
Open
Conversation
This was
linked to
issues
Jun 15, 2026
Matthbo
requested changes
Jun 15, 2026
|
This was referenced Jun 15, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Server (CsrfCookieFilter) → Set-Cookie: XSRF-TOKEN → browser stores it
browser (api.ts) → reads cookie, sets header → X-XSRF-TOKEN on POST
Server (CsrfFilter) → header == cookie? → yes → allow
The reason the filter was needed is that without it the server never issued the cookie in the first place, so the frontend had nothing to read and copy onto the request. The filter supplies the token (via a response cookie) and the frontend is what actually attaches it to requests.
This also directly solved issue #548