Got a client who has a website accessed over the local area network (emphasis, not over the internet). The previous version of the website was installed incorrectly as a virtual directory under the default website. So, everyone was used to going to the following address:


After installing a major update, the server was configured correctly and the web application was set up as the default on the server.


Of course, everybody is now complaining that their URLs don't work anymore. How can I configure IIS6 to un-break their bookmarks?


Reinoud's solution is probably the quickest fix (a bit "low-tech" but it works).

http://www.highposition.net/301-redirect-tutorial-iis/ (or any of a number of other sites Google returns for "IIS 301 redirect") has information on setting up 301/302 redirects for the "HTTP-clean" implementation, complete with screenshots.


The quickest way would be to create a directory called MyWebApp on the new location containing an index.html file with the following:

<meta http-equiv="refresh" content="0;URL=http://example/" />
  • I was hoping for more of a 301 type redirect.... – Ripped Off Aug 31 '10 at 13:31
  • ... Or configure IIS to do a HTTP/301 ("Moved Permanently") Redirect. – voretaq7 Aug 31 '10 at 13:32
  • Ah, since you where explicitly refering to a lan web application I assumed there was no real need for a 301, as http 301 type redirects are mostly used for SEO purposes. – Reinoud van Santen Aug 31 '10 at 13:35
  • Well, that's the thing; I'm not exactly sure what's the best choice. I'd prefer a less... hacky... way of doing this. A redirect (301 or otherwise, SEO be damned) seems a better route. – Ripped Off Aug 31 '10 at 14:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.