When I check the box for a page in DNN to be secure, that page all of a sudden gives me the "This page isn't redirecting properly" error from Firefox.

I can set the page to the URL of itself with https:// but I can't use the force https:// feature provided by the Secure? checkbox.

Any help?

DNN 4.6.0

Firefox  2 for Mac

Firefox 2 for PC

Internet Explorer 6 for PC

Internet Explorer 7 for PC

Windows Server 2003, IIS 6 for hosting the web site, with MS SQL 2000

https://micounties.org/MACPAC/DonatetoMACPAC/tabid/121/Default.aspx

Right now, we have the page set up as a URL to "https://micounties.org/MACPAC/DonatetoMACPAC/tabid/121/Default.aspx", and NOT with SSL enforced or enabled through DNN.

If we check the box for "Secure" we get the redirect error

All I know is the DNN team hasn't responded to my related post on this issue.  I was running 4.5.5 and just upgraded to 4.6.2, and have the same issue on both installations.  These are the steps I take to set up a secured login page:

- new page named "Secure Login" with Account Login module loaded
- enabled SSL on site
- set "Secure Login" page to secure
- picked "Secure Login" page as the login page for the portal

I have 1 SSL certificate that I share between multiple portals, secure.domain.com.  My portal is test.domain.com, and I have the SSL URL set to secure.domain.com/test.  The standard url is set back to test.domain.com.  The SSL Enforced checkbox is ticked.

When I try to login from a "secured" site it works fine once, from then on out I get all sorts of odd behavior.  After logging out and re-logging in I get redirected to the http://secure.domain.com portal.  If I go back and hit the refresh button on the login page, it plops me into the portal.  But, anything I click on takes me to the design of the Secure Login page for the test.domain.com portal.  If I have another secured portal setup in the same manner and I navigate to that, it takes me to the design of that portal's Secure Login page!  I have to run with the secure login page off in order for anything to work.

Also, the standard address is never re-introduced once it has switched me over to the secure.domain.com address.  That's not as big an issue, but I thought I'd point it out.

Could this be some sort of server caching issue or something?  I have caching turned on for performance reasons.