问题描述
现在，我对301重定向没有任何问题，但是有人问我如何为浏览器和搜索引擎撤消缓存的301重定向，因此我回答通过将301重定向回原始网址 ，至少那是我认为的解决方案，直到我看到有人提到您无法执行301重定向回
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 backhttp://getluky.net/2010/12/14/301-redirects-cannot-be-undon/http://www.velocityreviews.com/forums/t500058-undo-301-redirect.html
这是一个惊喜，我不确定是否是真的，所以我要问的是正确方式将缓存的永久301重定向从/a.html页还原到/b.html页，再还原回原始/a.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.
推荐答案
如果东西没有永久移动（永远！），请不要使用301。
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.
作为一种解决方法，您可以为a.html创建同义词（在服务器上，如 ln -s a_foo.html a.html ），然后从b.html重定向到a_foo.html
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
这篇关于如何撤消301重定向？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！