8

Now, I don't have any problems with 301 redirects, but one person asked me for the way to undo cached 301 redirects for browsers and search engines, so I replied "by doing a 301 redirect back to the original url", at least thats what I thought was the solution, until I saw people mentioning that you can't do a 301 redirect back http://getluky.net/2010/12/14/301-redirects-cannot-be-undon/ http://www.velocityreviews.com/forums/t500058-undo-301-redirect.html

this was a surprise and I don't know for sure if it's true, so what I'm asking is, what would be the proper way to revert a cached permanent 301 redirect from page /a.html to page /b.html back to the original /a.html ?

I would like some experts opinions.

Timo Huovinen
  • 53,325
  • 33
  • 152
  • 143

2 Answers2

3

Don't use 301 if the stuff hasn't moved permanently (forever!). This would be the proper solution.

The problem is that caching is done on the client side so you need to wait for that cache to timeout, then the client will again get the original page.

As far as I know this cannot be done in your situation from the server side.

As a workaround you could create a synonym for a.html (on your server, like ln -s a_foo.html a.html) and redirect from b.html to a_foo.html

Angelo Fuchs
  • 9,825
  • 1
  • 35
  • 72
1

If your problematic redirect is only on HTTP, Change to HTTPS. Or change example.com to www.example.com, or the other way around.

rosell.dk
  • 2,228
  • 25
  • 15