3 ms·
Another good example of this might be the transition from http to https. Granted, that's not actually the domain name but most people probably wouldn't make the
by codazoda 3y ago
Another good example of this might be the transition from http to https. Granted, that's not actually the domain name but most people probably wouldn't make the distinction. Although HTTP URL's still work on most TLDs in most browsers, most sites have transitioned to HTTPS. Further, HTTP might not always be supported by browsers, and as a site owner you don't have a lot of control over that. There are some solutions to protocol changes, such as redirecting, but that too could fail down the road.
The internet is so ephemeral and at the same time feels rather permanent.
- MereInterest 3y agoIn terms of backwards compatibility, I think that would be an easier one to resolve. Returning a 308 (Permanent Redirect) for all http requests to a https version is a single catch-all rule.
- FinnKuhn 3y agoIsn't this what most websites are already doing? Just redirecting http://example.com/test1 http://example.com/test1 to https://example.com/test1 https://example.com/test1?
- MereInterest 3y agoCorrect. The parent post gave http to https as a type of link-breaking, and this is how the redirect is implemented to avoid breaking links.
- mock-possum 3y agoAny harm in just making it default browser behavior to first try the link as clicked, then try https if it fails? Possibly could lead to unexpected behavior for resources loaded in the background, but I can’t think of unwanted behavior l.
- asddubs 3y agothe worse part of this is embedded http content in a https site breaking due to changing browser policies. images are upgraded to https if possible, otherwise broken. script embeds are just unilaterally broken if the embed is http, even if https is available.