IssueRaiser

This is an annoying problem – even if your entire site uses HTTPS, users could be vulnerable if they ever follow an HTTP link or their br...

This is an annoying problem – even if your entire site uses HTTPS, users could be vulnerable if they ever follow an HTTP link or their browser's autocomplete doesn't update to use HTTPS. Strict Transport Security was designed to solve that problem partially by telling the browser to never make an insecure HTTP request: http://caniuse.com/#feat=stricttransportsecurity That's widely supported now but it does require your browser to have previously visited the legitimate site within the stored `max-age` period. Preloading ( https://hstspreload.appspot.com/ ) can close that further but increases the organizational commitment that your web developers will never break the all-HTTPS contract by mistake.

Posted by acdha on Sep 6, 2016, 3:56 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments

hackernews (Other)

This is an annoying problem – even if your entire site uses HTTPS, users could be vulnerable if they ever follow an HTTP link or their br...

acdhaSep 6, 2016, 3:56 PM

This is an annoying problem – even if your entire site uses HTTPS, users could be vulnerable if they ever follow an HTTP link or their browser's autocomplete doesn't update to use HTTPS. Strict Transport Security was designed to solve that problem partially by telling the browser to never make an insecure HTTP request: http://caniuse.com/#feat=stricttransportsecurity That's widely supported now but it does require your browser to have previously visited the legitimate site within the stored `max-age` period. Preloading ( https://hstspreload.appspot.com/ ) can close that further but increases the organizational commitment that your web developers will never break the all-HTTPS contract by mistake.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue