3 ms·
> Because once you deploy the https:// https:// address scheme, there is no going back. Unless you send the HSTS header, that's not true. Even so, you could ju
by iancarroll 12y ago
> Because once you deploy the https:// https:// address scheme, there is no going back.
Unless you send the HSTS header, that's not true. Even so, you could just set the HSTS expiry time to the certificate's expiry (which would have to be done within your code, sadly).
- cnst 12y agoWhat do you mean it's not true without HSTS? Do modern browsers now automatically switch to the http:// http:// address scheme if https:// https:// is no longer available? Because otherwise, unless you don't care about incoming links, bookmarks etc, there is indeed absolutely no going back, with or without HSTS. That's the problem, only solvable with opportunistic encryption. And if you have dozens of domains and subdomains, what would you do in 2 years if this only CA is then kaput? The value of their offering is definitely above 100 USD, it would appear.
- technomancy 12y ago> Do modern browsers now automatically switch to the http:// http:// address scheme if https:// https:// is no longer available? Browsers do not, humans do.