Prevent conflict between CsrfComponent and CsrfProtectionMiddleware#591
Merged
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
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.
I am currently playing with next version of Cake (3.5.x). 🎉
Since
CsrfComponentis deprecated starting from 3.5, I have switched my app toCake\Http\Middleware\CsrfProtectionMiddleware.CakeDC/Users makes use of
CsrfComponent, so, whenCsrfProtectionMiddlewareis enabled application wide,CsrfComponentenabled in CakeDC/Users overridesCsrfProtectionMiddlewareinjected_csrfTokencausingCsrfProtectionMiddlewareto throw aInvalidCsrfTokenException.Currently, i am using this code in my
AppControllerto disableCsrfComponentfor CakeDC/Users pluginHowever, it would be better to check if
_csrfTokenis already defined in request param before loadingCsrfComponentto prevent overridingCsrfProtectionMiddlewareinjected_csrfToken. 😉