Solution to the dotnetnuke redirection looppublished on 4/12/2009 10:44 AM
If you have been setting up dotnetnuke websites for a while you have probably got this very annoying error. The error shows up by firefox telling you that it has prevented a redirection loop. IE on the other hand doesn't tell you anything however if you watch the packets you see that you get a constant stream of 302 redirect responses from the web server.
A few fixes has been found to this issue as can be seen [url:here|http://www.bestwebsites.co.nz/dotnetnuke/solving-the-dotnetnuke-redirect-loop/] and [url:here|http://weblogs.asp.net/christoc/archive/2008/06/19/dotnetnuke-homepage-won-t-load-keeps-redirecting.aspx] but they revolve around the problem having to do with the trust level set on the web site. The sites I set up are using fulltrust so that wasn't the case. What however fixed it was to add the hostheader in IIS. Normally you setup your site on a specific port and just tell IIS to catch any web request that goes to that port. You can still keep that but you will also need to add any aliases you have for your site as new entries. This will fix the problem once and for all.