Hi,

My company is moving our DNN portals from an internal-only server farm to one that also allows internet access (still login only). We have a reverse proxy (IBM's TAM) that the traffic needs to go through, and I've not been able to make it work yet.  Since our TAM is currently set up to require https connections, it looks like where its failing is that when you initially get to DNN to do the initial redirect to the default portal, its trying to do http in stead of https, which TAM then is not happy with. 

Has anyone set up DNN with a reverse proxy? I talked to the network folks, and I guess we could set TAM to allow http, and then set up all the SSL via DNN's SSL capabilities (we're using DNN4.5.5), but it seems like it would be better to utilize the SSL on the TAM network portion. 

Any advice?

Phil

I would try experimenting activating the https functionality of DNN first up.  By turning this on, you'll get a forced https page on all those pages marked as such.  This will probably get you going by the sound of it.

With regards to the UrlRewriter, yes, by design, all modules use it to generate their Urls.  No, in practice, people take short cuts and don't use the Url Rewriter to generate the Urls.  Which one you get depends on which modules.  The core modules are better in this respect than some third party modules.

If you look in the Url Rewriter code, you'll just find that the necessary code to force https on pages is already there - you just need to switch it on.