Allow redirecting `www` to base custom domain, or vice versa

[starkle]

I notice the default custom domain configuration results in both the base domain and the www subdomain being valid. I would rather make one or the other canonical, and make one redirect to the other. Having 2 valid URLs doesn't feel right. AFAIK this is not possible on the DNS side alone and requires the application to implement HTTP redirects.

[HermanMartinus]

@starkle This is doable in your domain registrar/manager. It's generally called Redirects or Page rules, or something along those lines. Give it a Google or ask your LLM of choice how to set it up with your current registrar.

It's generally best to do this at the DNS level since it doesn't make sense to do a round-trip for redirecting every time.

Regardless, while both www and root do resolve to the same site using the default setup, the canonical url tag is set which specifies which of the two is the "correct" one (more for search engines than anything else).

Feel free to ping me here or via email if you get stuck, or is your DNS manager doesn't have the option and I'll help you out.

[starkle]

@HermanMartinus Google and LLMs tell me the DNS configuration can make the www subdomain resolve to the same IP address as the root domain, but not issue a redirect - they say that requires an HTTP redirect. I don't want both www and the base domain to resolve validly. I would like one to redirect to the other.

I use Porkbun as my registrar. They have a URL forwarding option, but it requires using their SSL cert, which I don't want to use. It also works as an HTTP redirect service, so it's not happening at the DNS level anyway. Maybe this isn't the service you meant but it's the only close match. I agree DNS level would be better but I don't think it's technically possible.

Last thought - it wouldn't be doing a round-trip for redirecting "every time", only the first time. Once the user is redirected, they are in the canonical path and shouldn't encounter further redirects when browsing.

[HermanMartinus]

@starkle Huh, you're completely right. It does seem that Porkbun does make URL redirection pretty difficult and does require using their certs.

I've added www redirects to my to-do list, but with low priority. In the meantime you can add this script to your head directive to achieve the same thing, including preserving the path. And yes, it will only do it on the first time per user using the www subdomain.

<script>
if (window.location.hostname.startsWith("www.")) {
  const rootDomain = window.location.hostname.slice(4);
  const newUrl = `${window.location.protocol}//${rootDomain}${window.location.pathname}${window.location.search}${window.location.hash}`;
  window.location.replace(newUrl);
}
</script>

[starkle]

@HermanMartinus Thanks, I'll give that a try! Shall this issue be reopened in the meantime so the progress can be tracked?