TOML Redirects not working

Support
, , ,
#1

I have 3 websites hosted at netlify:

But I’m using https://vee-validate.logaretm.com website to redirect to them using a .TOML redirects file:

[[redirects]]
from = "/v2/*"
to = "https://vee-validate-v2.netlify.app/:splat"
status = 200
force = true

[[redirects]]
from = "/v3/*"
to = "https://vee-validate-v3.netlify.app/:splat"
status = 200
force = true

[[redirects]]
from = "/v4/*"
to = "https://vee-validate-v4.netlify.app/:splat"
status = 200
force = true

[[redirects]]
from = "/"
to = "/v4/"
status = 302
force = true

This front-facing website has no other files but the .TOML file. It is only used to redirect users to either of these websites depending on which version they want to see.

That means each of those websites should be accessible with:

  • https://vee-validate.logaretm.com/v4/
  • https://vee-validate.logaretm.com/v3/
  • https://vee-validate.logaretm.com/v2/

This has worked great for the past year. I had not deployed anything in December but for some reason, all of the websites are reporting 404 errors randomly since yesterday. I re-deployed the websites and they work for about 5 minutes before they go down again with 404s.

Is this a global issue or did something change?

#2

From what I can see, the paths are incorrectly configured. I could check your deploy to see the file paths, for example, this is one of the paths: /assets/js/49.6532be3e.js. But you’re loading it from: /v2/assets/js/49.6532be3e.js. Thus, it’s 404-ing.

#3

Thanks for the reply, what I don’t get is why is it randomly working and failing. I can refresh 5 times and I get varying responses from a total page 404 to partial 404s to working just fine.

For example this URL is right here:

Now this should use the 3rd rule (or 4th) and serve stuff/assets from

Right? instead, it uses the first rule and serves stuff from

Furthermore, when I click on any of the failed assets and open the file in a new tab it gives 404 but when I refresh a couple of times and it works. What’s going on here? at least it should be giving 404 consistently?

Please note that all that stuff worked just fine for more than year, I hardly changed anything about the deployments and I tried reverting to months old deployments with no luck.

#4

I don’t see how these can ever not serve 404s, the files clearly don’t exist where you’re trying to request them.

Could you share the request ID headers or the HAR file recordings of the times when they don’t return a 404?