Add CSRF protection to internal requests #474
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
RobinDaugherty
force-pushed
the
feature/add-csrf-to-requests
branch
from
901f724 to
5fcee47
Compare
RobinDaugherty
force-pushed
the
feature/add-csrf-to-requests
branch
from
5fcee47 to
ef06461
Compare
and refactor the specs to be more clear.
RobinDaugherty
force-pushed
the
feature/add-csrf-to-requests
branch
from
47abbd0 to
4f05b45
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.
Better Errors accepts requests from its own Javascript components in order to provide variables and evaluate console commands. These are now protected by a CSRF token that's set as a cookie when the error page is rendered.