Skip to content

Strategy for reading the actual CSRF token from the request #7539

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
rwinch opened this issue Oct 17, 2019 · 0 comments
Open

Strategy for reading the actual CSRF token from the request #7539

rwinch opened this issue Oct 17, 2019 · 0 comments
Labels
in: web An issue in web modules (web, webmvc)

Comments

@rwinch
Copy link
Member

rwinch commented Oct 17, 2019

Summary

Currently the CsrfTokenRepository allows loading the expected CsrfToken from the request. It would be nice if the actual CSRF token could be a strategy that could be replaced.

Related gh-7537 gh-7538
@rwinch rwinch added the in: web An issue in web modules (web, webmvc) label Oct 17, 2019
@rwinch rwinch added this to the 5.3.x milestone Oct 17, 2019
@rh-id rh-id mentioned this issue Mar 17, 2020
Closed
@rwinch rwinch removed this from the 5.3.x milestone May 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
in: web An issue in web modules (web, webmvc)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rwinch