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
If your problematic redirect is only on HTTP, Change to HTTPS. Or change example.com to www.example.com, or the other way around.
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