Domain level redirects and wildcards

[coelmay]

Hi @lukehler

@lukehler

Can I use http*://... to match both http and https?

No.

@lukehler

Can I use https://*domain.tld/* to match with or without a subdomain?

No.

@lukehler

using a _redirects file in a “site” with no build command or public folder?

_redirects go into the directory that is published, there is no requirement that it has a specific name (e.g. public) and no requirement for a build command.

@lukehler

I couldn’t seem to get this working in the _redirects file and had to use toml

In _redirects format the above rule would read

http://www.custom-domain.tld/*    https://destination.tld/path    301!

@lukehler

Is there any concern over generating a _redirects or netlify.toml file with a build script?

Have done this myself. As long as the formatting is correct no issues (that I have found).

@lukehler

I’m guessing _redirects might work

Redirects are part of post-processing (post-build.)

@lukehler

a single example right now - serene-austin-54062e.netlify.app - covering two variant domain names

Of course, as you don’t appear to wish to mention the domains you are using/testing it is impossible for anyone to test the behaviour for you. If you wish to have serene-austin-54062e.netlify.app redirected elsewhere, you will need to put in a rule for that too, otherwise a blank page will load.

@lukehler

Any traffic to any version of custom-domain.tld gets forwarded to the same destination.

If regardless of the custom domain visited (example.com, site.com, website.com, etc.) the destination is always the same (e.g. mywebsite.com/path) then you can have one rule to cover everything

/*    https://detination.tld/path    301!

_redirects or netlify.toml

[[redirects]]
  from = "/*"
  to = "https://destination.tld/path"
  status = 301
  force = true

This would cover any custom domain as well and the <site>.netlify.app domain too.