Hi All,

I have been working on an issue for quite a while now and cannot seem to figure out what is happening.  I am hoping someone here can shed some light.  Here is the scenario:

We have a system setup on a Windows 2008 R2 server with IIS 7.5 and SQL Server 2005 (64 bit).  We have two portals setup and portal 0 redirects to portal 1 when a user clicks on a button in a module we have built.  We have been using this module for years and it works everywhere else other than on this one system. 

The problem we have encountered is that while the redirect works fine with FireFox, Chrome, Opera, etc..., with IE it does not work.  We installed Fiddler on the server and what we have found is that in IE, the redirect goes into an infinite 302 redirect loop and eventually times out with a message that it cannot resolve the host.  We have checked routing, NAT, firewall rules, and even put the web addresses in the hosts file so there was no external factors affecting the routing.  It still happens.  What is very strange about it though is that it only occurs on an authenticated user.  If you are not logged into the system, the redirect works fine.  Additionally, if you are logged in as host, the redirect works fine.  It is only when you are logged in as a regular user using IE, that you encounter the infinity 302 redirect loop.

If anyone has any ideas or has encountered something similar, your help would be greatly appreciated.

Thanks,

Tom

Hi Sebastian,

 Thanks for replying.  It appears that the issue had to do with authentication cookies not being either applied or accessible between parent portals.  This is kind of strange considering the other portal was setup as a public portal.  I recreated the secondary portal as a child portal and the issue went away.  What I am finding strange though is that this only happened with IE.  The urls are fairly similar with the exception that the secondary URL had a about 8 encrypted query strings.

Thanks,

Tom