Redirect pitfalls with HTTP Strict Transport Security and some solutions
coderrr.wordpress.com
Redirect pitfalls with HTTP Strict Transport Security and some solutions
1–4 of 4 posts
Re: Redirect pitfalls with HTTP Strict Transport Security and some solutions
#2What bugs me is that whatever solution you'd want to use requires two SSL certificates and with that, at least two distinct IP addresses.
Especially the latter is concerning considering we are running out of addresses.
Re: Redirect pitfalls with HTTP Strict Transport Security and some solutions
#3What bugs me is that whatever solution you'd want to use requires two SSL certificates and with that, at least two distinct IP addresses. Especially the latter is concerning considering we are running out of addresses.
No, most CSAs these day will automatically add "www.yourdomain.com" to your certificate as a Subject Alternate Name.
Re: Redirect pitfalls with HTTP Strict Transport Security and some solutions
#4What bugs me is that whatever solution you'd want to use requires two SSL certificates and with that, at least two distinct IP addresses. Especially the latter is concerning considering we are running out of addresses.
[deleted]