QUOTE (mariposa @ Jan 19 2010, 01:01 AM)

I just got a Network Solutions SSL cert and enabled SSL on my NetworkSolutions DotNetNuke portal and now I'm in an infinite loop of redirects.
(IMG:
http://forums.networksolutions.com/style_emoticons/default/dry.gif)
While I was waiting on the Website Restore feature to finish I did some research.
It turns out this is common to DotNetNuke, requiring some workarounds on the part of the hosting provider:
http://www.purpleant.com/Blogs/BrianSwanso...-redirects.aspxhttp://www.dotnetnuke.com/Community/Forums.../2/Default.aspxAnyone been able to get SSL working at least for the login portion of using a portal?
Our proxy SSL doesn't allow server-side variables to detect HTTPS (secure). All server-side coding will always detect HTTP (non-secure), and for programs that attempt to redirect non-secure connections (http://) to a secure connection (https://) will result in an infinite loop and server error after 30 seconds.
The only ways around this is to
assume the connection is secure by making all the links to the sensitive pages https, or
use a client-side program (like javascript) to detect if it's secure and redirect if it's not. The coding below will do just that. Just modify it to redirect to the correct secure domain and add it into the HTML of any sensitive pages.
CODE
<script language="javascript">
if (document.location.protocol != "https:")
{
document.location.href = "https://secure.domain.com" + document.location.pathname;
};
</script>
I hope this is helpful,