Jeez that's a heck of a redirect chain. The :443 is an odd choice no? And the redirect to https://domain before https://www.domain. There are even two more for me. Also... inconsistent casing for the Location header? Different parts of the server stack I suppose.
Sure, it just seems odd to specify it. I haven't seen that in a link in a long time. I don't usually snoop Location redirect chains in my browser though, so maybe it's more common than I think.
Comments
Jeez that's a heck of a redirect chain. The :443 is an odd choice no? And the redirect to https://domain before https://www.domain. There are even two more for me. Also... inconsistent casing for the Location header? Different parts of the server stack I suppose.
443 is just the default https port, so not really? It doesn't add anything as browsers use that port by default when the scheme is https.
Sure, it just seems odd to specify it. I haven't seen that in a link in a long time. I don't usually snoop Location redirect chains in my browser though, so maybe it's more common than I think.
http:// → https:// → https://www. is actually the recommended technique, because it lets an HTTP-Strict-Transport-Security subdomains directive work.
But the rest could have been flattened into the second redirect.