4 ms·
Nobody's saying it does - including Chrome. The browser will simply (and correctly) show "Not Secure" in the address bar when next to the url viewing your blog.
by hughes 8y ago
Nobody's saying it does - including Chrome. The browser will simply (and correctly) show "Not Secure" in the address bar when next to the url viewing your blog. If a user doesn't have an expectation of security, they won't be bothered or perhaps even notice.
- deleted 8y ago[deleted]
- ysavir 8y agoWhich is great for users that understand what these security concerns are all about, like typical HN folk. But these people are probably aware of cyber security already, so not much gain here. And people that _don't_ understand cyber security will have no context for what "not secure" means, and may needlessly avoid a variety of HTTP static-HTML sites, where these security issues aren't that great a concern.
- sarif 8y agoUm, good? If people avoid your site because its not secure, maybe you should fix it?
- NeoBasilisk 8y agoWhat does it mean to fix a site that does not accept/process POST requests?
- UncleMeat 8y agoStart serving over https? Since when has encryption only mattered for POST?
- NeoBasilisk 8y agoCan you explain the benefit in other situations? Preventing MitM attacks is the only thing I can think of.