If you are using the web.config setting UsePortNumber=True for multiple secure portals with SSL certs bound to different port numbers on same IP address, would you please report on any experience (success or failure) with DNN 5.4.1 and the new DNN 5.4.2 which I understand should be released on 5/19 tomorrow.

Could you please clarify whether you are using a scenario with all pages secured on a given portal or mixed  where some pages are secured and some pages are not secured on the particular portal?

Regardless of your scenario, could you also please clarify what set of portal aliases you have used? In particular, portal aliases with and/or without which ports in which order? Clarifying with "standard http port 80", "standard https port 443", "my non-standard http port", or "my non-standard https port" would be helpful?

Finally, stating whether you got everything to work with FriendlyUrlProvider turned on would be interesting to know. See the issue reported in this post

http://web3.dotnetnuke.com/Community/Forums/tabid/795/forumid/108/threadid/361312/scope/posts/Default.aspx

for more discussion of the problems when the friendly url provider is turned on. I haven't ever managed to make UsePortNumber work unless I turn off the friendly URL provider. I consider this a major issue, and I hope the DNN gurus will turn their attention to this problem.

CT

---

CT