If it is possible, I would like a more definitive answer to the question of SSL and DNN.
I have read in the Roadmap section of this site (http://www.dotnetnuke.com/Development/Roadmap/SSL/tabid/654/Default.aspx) where it states that "Currently, DotNetNuke does not officially support SSL." I have also read in other forum posts where people have discussed setting up IIS to run DNN with SSL and then other discussions which delve into using one of the many (for purchase) modules which can handle SSL centric pages (ie login or whatever else kind of page the user would want protected).
We are currently experiencing an issue in getting a DNN site up and running and we believe it is related to DNN and SSL.
We are a government site and are required to run SSL on every server/website we have. After a successful install of DNN 4.5 on one of our servers (again we only handle only https request), we are having an issue with the default DNN site not working. In ie6, the site just has a continuos processing status and the page never loads. In Firefox, the error stated in the browser reads "The page isn't redirecting properly - Firefox has detected that the server is redirecting the request for this address in a way that will never complete."
A user is able to access select files within the directory folder as in logo.gif, but the website's default.aspx does not process.
We do have a "test" 4.4.1 DNN application running quite successfully on a development server that does not have SSL.
So it appears with our testing, that without somekind of purchase of a third party module (and it would seem that even with something like that, that our problem is still not solved because we can't get the site to even come up in a default state). That we are not going to able to use DNN.
We look forward to the clarification of our delimma that only this forum can provide. Thank you for your time.