I have set both of my portal domain names to the /DNN subdir in my shared hosting server root directory.
And within DNN I have 2 aliases for the primary portal - e.g. www.myhostingdomain/dnn which I think was put there by default and that I cannot edit and www.domain1.com which I added. For the second portal that I defined I set www.domain2.com as the alias.
My first portal works but the edit bar gets the redirected URL of www.myhostingdomain/dnn no matter whether I type in www.domain1.com or www.domain2.com and I have never been able to get a new portal view for my second portal as I always get the domain1 view.
Interestingly, if I set host settings to have my second domain the default portal and then enter in the second portal URL I seem to just hang and get no response back at all. From either portal URL.
I thought I may have just locked myself out of my site but entering www.myhostingdomain/dnn still worked. The 2 portal domains seem to not respond at all after several minutes. SOrt of tells me either portal URL alias is not working but rather only the redirected actual hosting URL with the /DNN subdir.
When I see doc on the alias names they are of the form www.portalname.com with no http:// header or subdirectory decorations. SHould they be something else to not cause the 302 redirect???
Is a 302 redirect normal for DNN to send to the browser? Seems at best a waste of turnaround.
Thanks, Dave
Doing some more testing I have an update:
If I use an HTTP header viewer and GET www.myhostingdomain/dnn I am returned a 302 redirect whereas if I GET www.myhostingdomain/dnn/ with the trailing / I get the expected 200 OK header. Could this be the reason my aliases are not working? They are getting 302 FOUNDs and were redirected to my actual hosting dir URL originally until I switched the default portal to the second portal I created and now the 302 resposnes redirect to the 2nd portal which never responds. I tried various combinations of terminating / and /DNN suffices to no avail.
After a bit more testing the non response seems to be a 302 request loop. If I enter either portal name rather than the hosting URL the browser hangs saying "Connecting" and spins the box around 10% busy until I stop the browser.
And after setting the host back to the default portal, the one with the actual hosting URL alias of www.myhostingdomain/dnn I am back to my original problem where both my portal names resolve to www.myhostingdomain/dnn/ and show the first portal website.
At minimum, seems like DNN is doing some strange redirecting and not recognizing my portal URL names.