feat: allow to rename xsrf-token #56268
Open
+4
−2
Conversation
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
Barbapapazes
force-pushed
the
feat/allow-to-rename-xsrf-token
branch
from
2cf696b to
639a240
Compare
Barbapapazes
force-pushed
the
feat/allow-to-rename-xsrf-token
branch
from
639a240 to
eb2f730
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello 👋,
This is a following PR to the issue #56238.
It introduces a new configuration option
xsrf-tokenin thesession.phpconfiguration file, allowing developers to customize the name of the XSRF token cookie. I'm unsure about the name of this field.Also, I had to read the config from the static method
serializedin theVerifyCsrfTokenmiddleware. I'm unsure if this is the best way to do it, but it works.