fix: handle stale CSRF tokens gracefully#54
Merged
Conversation
…ecting When deploying behind reverse proxies or switching between environments, stale CSRF cookies cause 403 errors. Instead of showing an error, clear the invalid cookie and redirect back so a fresh token is set automatically. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
Context
When deploying behind reverse proxies (e.g., Cloudflare → Traefik → App) or switching between local dev and production, browsers may hold stale
XSRF-TOKENcookies that don't match the server's expected token. This causes a 403 Forbidden error on any POST request (login, form submissions, etc.) with no clear way for the user to recover other than manually clearing cookies.Test plan
🤖 Generated with Claude Code