Skip CSRF protection check on callback route #2
Conversation
This file contains 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
This route only gets hit by callbacks from PayBright, which won't have a CSRF token set, and will error if we have CSRF protection enabled in our app.
adammathys
approved these changes
Jul 27, 2017
luukveenis
force-pushed
the
skip-csrf-protection-on-callback
branch
from
aac947a to
7826cb4
Compare
I took this from some of the other Solidus extensions because builds for all Solidus versions 2.0+ started failing with dependency resolution issues.
luukveenis
force-pushed
the
skip-csrf-protection-on-callback
branch
from
7826cb4 to
6aebf61
Compare
|
This makes sense, thanks |
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.
This route only gets hit by callbacks from PayBright, which won't have a CSRF token set, and will error if we have CSRF protection enabled in our app.