You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
NYTimes no longer good example of captive portal trigger #8175
If you go to a website that isn't protected by HTTPS Everywhere (currently, nytimes.com is one such site)
Actually, the site has to be protected neither by HTTPS Everywhere nor by HSTS.
The New York Times is moving to HTTPS according to "HTTPS on NYTimes.com". The device that I'm using right now provides no HSTS indicator as of yet, but I imagine it may be added soon. And if not, expect somebody to submit a pull request adding it.
Activity
jeremyn commentedon Jan 11, 2017
Any site that isn't in the HSTS preload list is a valid target for HTTPS Everywhere, for example see https://www.eff.org/https-everywhere/faq#why-does-https-everywhere-include-rules-for-sites-like-paypal-that-already-require-https-on-all-their-pages. I agree though that now that the NY Times partially supports HTTPS, the FAQ shouldn't use it as an example, just to avoid confusion.
Pinging @Hainish to modify the FAQ.
Hainish commentedon Jan 11, 2017
Great! This can actually be implemented via a PR since the FAQ is now generated from markdown in the repo:
https://github.com/EFForg/https-everywhere/blob/master/docs/faq.md
pinobatch commentedon Jan 11, 2017
In #8180 I recommend Example.com
jeremyn commentedon Jan 12, 2017
I've merged the FAQ change from nytimes.com to example.com in pull request #8180 , so I'm closing this issue.