3 ms·
>> Normally, when a site changes URLs, you can use a redirect to send visitors to the new address. But, if the old address is HTTPS, that doesn't work: the old
by yjftsjthsd-h 3y ago
>> Normally, when a site changes URLs, you can use a redirect to send visitors to the new address. But, if the old address is HTTPS, that doesn't work: the old address will display a misleading security warning instead of redirecting.
> That too is an outright fabrication. I just tried a 301 redirect from HTTPS to HTTP and it worked fine, on up-to-date Firefox, no security warning. Maybe the author promised to never get rid of TLS with a `Strict-Transport-Security` header? Don't do that?
I think the author wants to be able to move a site by setting the old domain's DNS to point at the new site's server and have the server 301 all/old domains to the new domain. Which... you can still do, just with HTTPS in play you have to handle certs for any old domain(s) you're redirecting.