Re:Fencing Your SSL Errors With HSTS
by MichaelGG on Sunday January 20, 2013 @11:21AM
(#5087272)
It's also useful if your app requirements trump deployment requirements. You might want a particular app to always require SSL, regardless of how it is deployed.
Re:Fencing Your SSL Errors With HSTS
by mguillemot on Sunday January 20, 2013 @07:14AM
(#5086692)
It prevents anyone controlling the DNS resolvers of your clients to redirect to faked HTTP website (of course, only for those of your clients who already visited your real website).
Imagine you're using my WiFi connection. Without HSTS, I could redirect you to a fake http://www.facebook.com to steal your login credentials if you do not notice the login page is not served over HTTPS (and let's be realistic: most non-technical people won't notice something that's supposed to be there, but is not).
Edit: also, because of HSTS I can only visit your "secure" site and can no longer get to your marketing page to see what it is you do.
[0] https://github.com/kennethreitz/flask-sslify
http://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
Doesn't this just add more complexity to a problem that is not that hard to solve?
Imagine you're using my WiFi connection. Without HSTS, I could redirect you to a fake http://www.facebook.com to steal your login credentials if you do not notice the login page is not served over HTTPS (and let's be realistic: most non-technical people won't notice something that's supposed to be there, but is not).