Removing http301 redirect from client's cache

Posted by ChessWhiz on Stack Overflow See other posts from Stack Overflow or by ChessWhiz
Published on 2010-04-03T21:13:50Z Indexed on 2010/04/03 21:23 UTC
Read the original article Hit count: 438

Filed under:
|
|
|
|

Hi,

I have a server/client architecture where the client hits the ASP.NET server's service at a certain host name, IP address, and port. Without thinking, I logged on to the server and set up permanent HTTP301 redirection through IIS from that service to another URL that the machine handles via IIS (same IP and port), mistakenly thinking it was another site that is hosted there. When the client hit the server at the old host name, it cached the permanent redirect. Now, even though I have removed the redirection, the client no longer uses the old address. How can I clear the client's cache so that it no longer stores the redirect?

I have read about how permanent HTTP301 can be, but in this case, it should be possible to reset a single client's knowledge of the incorrectly-learned host name. Any ideas?

© Stack Overflow or respective owner

Related posts about 301-redirect

Related posts about redirect