How does it take for a redirect to unresolve?

I added a redirect (rewrite using the 200) to my .toml config which was incorrect. I’ve tried updating it but it continues to redirect to the old location. After fixing the redirect, how long does it take to see the change? I assume it’s waiting for the new DNS to resolve?

Hey @ddamato

What does the netlify.toml look like?

The redirect should invalidate immediately. It might be a caching issue. Can you share the link?

Hi @ddamato!

DNS shouldn’t be an issue here. (Assuming you already have a domain pointing to your site). Once the requests are hitting your site on Netlify, the redirects should be able to do their thing.

I’d expect new rules to take action right away after a deploy.

Here’s the .toml

[build]
  command = "npm run build"
  functions = "lambda"
  publish = "web"

[[redirects]]
  from = "/api/*"
  to = "/.netlify/functions/:splat"
  status = 200

[[redirects]]
  from = "/rss/*"
  to = "https://deltazeus.s3.amazonaws.com/rss/:splat"
  status = 200

So https://www.deltazeus.com/rss/40.7_-73.9.xml should rewrite to https://deltazeus.s3.amazonaws.com/rss/40.7_-73.9.xml but instead goes to an old url
of http://www.deltazeus.com.s3-website-us-east-1.amazonaws.com/40.7_-73.9.xml (back when I forgot to include the /rss. It’s even a different bucket now (you can see the bucket deleted message).

Also just realized that you’re probably right about the caching, as it worked incognito and other browsers that haven’t used the new url yet.

Thanks for the insight!

1 Like