request: Omit CSRF token for non-validated requests#8509
Merged
Conversation
changelog: Internal, Performance, Exclude request forgery token from front-end requests when not required
mitchellhenke
approved these changes
May 30, 2023
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
3 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 of changes
Updates the
requestutility to avoid including the CSRF token if it is not necessary for the request.See related Slack discussion: https://gsa-tts.slack.com/archives/C0NGESUN5/p1685476447724009
Easier to review changes with whitespace hidden: https://github.com/18F/identity-idp/pull/8509/files?w=1
📜 Testing Plan
yarn testIt's easier to test the latter by setting a very low session timeout in local
config/application.yml: