I have a freshly posted site in DNN 3.1

My local copy of the site has portal aliases set as

0 - localhost/xyz
3 - localhost/xyz-a
4 - localhost/xyz-secure

This local copy resolves correctly and works just fine.

The "live" copy of the site has portal aliases set as

0 - www.xyz.com
3 - www.xyz-a.com
4 - secure.xyz.com

When I attempt to load www.xyz.com (I can see via HTTP Analyzer) the page repeatedly redirects to itself, infinitely. If I try to load xyz.com - without www. the same thing happens. This happens with all of my portal aliases.

The PortalAlias table is currently the ONLY difference (obviously besides the DNS information set for the domain) between each copy of the web site. I've checked the permissions on the home page in the site settings (via the database tables) and they match on my local copy and the live copy.

So, my question is pretty simple...what am I doing wrong? Why is this page redirecting to itself? Any input would be greatly appreciated.

Thank goodness...post has been approved! :)

Sadly, I did this first and now, 4 hours later, I'm still having the same problem.

I have confirmed that the changes are being pulled in from the database by altering the PortalAliases to point back to my development machine (localhost/xyz). This change, obviously, redirects me back to my own local copy which comes up just fine and all is well. Change it back to the actual domain (www.xyz.com) and the redirect loop happens. I've even tried to just use xyz.com without the www prefix and I still have the same looping problem.

Any other thoughts? Sorry if I sound pessimistic, but I'm extremely frustrated :(

Glad you got it working.

One thing that a lot of people do not realize is that there can be many different aliases for the same portal, so you can keep your local portal alias and your production alias in the DB, and they won't interfere with each other.

The reason I knew it was a cached portal alias is because the code will look through your aliases and then re-direct you back to the first one if none of them can be matched to the Url.  If you change the first one in the DB, then it causes this weird problem of an endless redirect.

If you add the portal alias through the UI it will not allow you to change the current alias for this reason.

If you are interested, you can read more about the details of PortalAlias here:

http://blogs.snapsis.com/PermaLink,guid,87c379cc-c700-4eb8-a48d-e778aeef65fa.aspx

 

---