Reset csrf meta tag based on presence of headers #200
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.
We're setting up authentication with devise and trying to just use the default session cookies. The only problem, as you probably already know, was resetting the CSRF token after sign-in/sign-out. Since we're already grabbing the token from the meta to send it up to the server, what do you think about adding the following to the
csrf.js
initializer template in the initializer?This approach is based on the following stack overflow post:
http://stackoverflow.com/questions/20875591/actioncontrollerinvalidauthenticitytoken-in-registrationscontrollercreate
We're setting these headers in an after filter on a custom
SessionsController
that inherits fromDevise::SessionsController
. It would still be on the developer to send those tokens back in a header somewhere, but I think that's reasonable.