3 ms·
This gets mentioned every time a blogpost from Netflix appears on HN. I've mentioned it too! https://news.ycombinator.com/item?id=12217900 https://news.ycombina
by diggan 10y ago
This gets mentioned every time a blogpost from Netflix appears on HN. I've mentioned it too! https://news.ycombinator.com/item?id=12217900 https://news.ycombinator.com/item?id=12217900
According to kpcyrd, this is what happens:
" I have the same issue, even though the link actually is http, my browser tries to open the https version, no matter what. It looks like https://netflix.com https://netflix.com had hsts with includeSubdomains at one point in time which my browser has still cached. "
- nathancahill 10y agoWhich is why you should only enable HSTS if you plan on supporting it permanently.
- peterwwillis 10y ago"But there's no reason to not use HTTPS! What could go wrong?" But, you know... we have to secure our blog posts from MitM...
- eterm 10y agoNo, you have to secure your blog posts because cookies against the top level domain can be in the request headers sent to the subdomain[1]. It's a bit bizarre you'd blame HTTPS, what is your alternative, don't use https? [1] I say "can" because it depends on how the top level cookie is set, whether the browser respects the secure flag, and individual browser versions.