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

Safari 4 supports http only cookie #25053

Merged
merged 2 commits into from
May 17, 2016
Merged

Safari 4 supports http only cookie #25053

merged 2 commits into from
May 17, 2016

Conversation

@rails-bot
Copy link

Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @chancancode (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@@ -722,7 +722,7 @@ The log files on www.attacker.com will read like this:
GET http://www.attacker.com/_app_session=836c1c25278e5b321d6bea4f19cb57e2
```

You can mitigate these attacks (in the obvious way) by adding the **httpOnly** flag to cookies, so that document.cookie may not be read by JavaScript. Http only cookies can be used from IE v6.SP1, Firefox v2.0.0.5 and Opera 9.5. Safari is still considering, it ignores the option. But other, older browsers (such as WebTV and IE 5.5 on Mac) can actually cause the page to fail to load. Be warned that cookies [will still be visible using Ajax](https://www.owasp.org/index.php/HTTPOnly#Browsers_Supporting_HttpOnly), though.
You can mitigate these attacks (in the obvious way) by adding the **httpOnly** flag to cookies, so that document.cookie may not be read by JavaScript. Http only cookies can be used from IE v6.SP1, Firefox v2.0.0.5, Opera 9.5 and Safari 4. But other, older browsers (such as WebTV and IE 5.5 on Mac) can actually cause the page to fail to load. Be warned that cookies [will still be visible using Ajax](https://www.owasp.org/index.php/HTTPOnly#Browsers_Supporting_HttpOnly), though.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you make it IE v6.SP1, Firefox v2.0.0.5, Opera 9.5 and Safari 4 onwards.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also Http only cookies --> HTTP only cookies.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can mention Chrome also? http://stackoverflow.com/a/528435/925734 ?

@prathamesh-sonpatki
Copy link
Member

@matkoniecz Thanks. Few comments and then good to go.

@maclover7 maclover7 added the docs label May 17, 2016
@matkoniecz
Copy link
Contributor Author

@prathamesh-sonpatki Done.

@prathamesh-sonpatki
Copy link
Member

prathamesh-sonpatki commented May 17, 2016

@matkoniecz Thanks! Can you also squash the 2 commits and add [ci skip] to the final commit message.

As this is doc-only change, [ci skip] will prevent travis from running tests.

@simi
Copy link
Contributor

simi commented May 17, 2016

@prathamesh-sonpatki I think "commiter" is able to do this via GitHub UI right now (squash commits and edit message).

@prathamesh-sonpatki prathamesh-sonpatki merged commit 17f04e4 into rails:master May 17, 2016
@prathamesh-sonpatki
Copy link
Member

I hadn't tried that on rails repo. But just did and I forgot to add [ci skip], anyways 😄

@matkoniecz matkoniecz deleted the Safari_and_http_only_cookie branch May 17, 2016 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants