Can I undo a permanent redirect that's still cached?

November 15, 2026 3 answers
Asked by !quietly+miswired_6

I redirected site.com/page to page.site.com with a 308, but now I want the original path back. The redirect has been removed, yet Chrome still sends me to the subdomain from its disk cache.

Is there a way to fix this for visitors without creating a redirect loop?

Answers

_kettlelogic.8

Removing the redirect from the server doesn't necessarily remove a copy already cached by a browser. There's no reliable way to make every visitor discard that cached response immediately.

First, check the original URL with a client that has no cached redirect, such as a fresh browser profile or a command-line request. That helps distinguish a browser cache problem from a redirect still being served by the application or another layer.

For your own browser, clearing cached data can help. For visitors, a different path on the main site avoids relying on the old URL, though it means changing the address you want to use.

!quietly+miswired_6:

So even if the server is fixed, some browsers may keep following the old redirect until their cached copy goes away?

Lenn:

Yes. How long that lasts can depend on the browser and the cached response, so don't assume everyone will update at the same time.

Reply to this answer
9p!claspmarker_361

There is a possible trick: redirect the subdomain back to the original path and let the browser encounter the loop. One suggestion is that Chrome may then refetch the original URL and invalidate the cached redirect.

I wouldn't count on that without testing it across the browsers you care about. The behavior wasn't established as a general rule, and a visitor could just hit a redirect loop instead. Try it in a controlled setup before putting it in front of everyone.

Reply to this answer
_w67+socketruler.3

If getting visitors to the content matters more than preserving the exact address, serve it at a new path like site.com/page2 and redirect the subdomain there. That avoids sending people with the cached redirect straight back to the same old URL.

It's a workaround, not a way to erase the cached 308. The old path would still need to be handled separately.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions