Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disabling CSRF via web-sockets accessed routes #2732

Closed
wants to merge 1 commit into from
Closed

Disabling CSRF via web-sockets accessed routes #2732

wants to merge 1 commit into from

Conversation

juulderuysscher
Copy link

When you do a post to a route which is in the sails.config.csrf.routesDisabled string via a web-socket CSRF was not disabled.

When you do a post to a route which is in the `sails.config.csrf.routesDisabled` string via a web-socket CSRF was not disabled.
@mikermcneil
Copy link
Member

@juulderuysscher hmm I'm not sure I'm ok with doing this-- if we disable CSRF for sockets, how will we deal with socket hijacking? Here's how we normally suggest using CSRF over websockets -- would you try that out? Let me know if you run into difficulties. Thanks!

sgress454 added a commit that referenced this pull request Jan 20, 2016
 -- Add req.originalUrl
 -- Compute req.path
 -- Compute req.query based on path
 -- Fix wantsJSON to allow `false` value, FWIW

refs #2732
ctartist621 pushed a commit to ctartist621/sails that referenced this pull request Feb 3, 2016
 -- Add req.originalUrl
 -- Compute req.path
 -- Compute req.query based on path
 -- Fix wantsJSON to allow `false` value, FWIW

refs balderdashy#2732
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants