On Mon, Feb 28, 2011 at 4:27 PM, Bing H Bang <[email protected]> wrote:I'd try that if I had another ip address. Also, putting a box in front of the firewall sounds dangerous.[ ... ]
What I'm trying to do is accept https traffic, decrypt it, pass it through untangle, then encrypt it back as it gets delivered to the https port of the web server.
This setup works in that I can point my browser at the https port of my untangle server and the web pages work properly.
What doesn't work is the untangle server shows no scanning activity when I access the web pages. I think the path webserver->untangle->webserver does not trigger the scanning in untangle because the traffic it sees is from an internal ip going to the same internal ip.
Interesting. Can you put another Web server box outside of Untangle to decrypt the traffic, then pass it through as normal? That could help with performance as well. Or use a second network connection to pass the traffic back out to Untangle's external interface?
My website is currently pretty simple. Maybe I'll start seeing problems when the site gets going for real. Hope not!Also, do you find that stunnel is able to work reliably doing HTTPS in this way? My recollection is that there is some difficulty with redirects generated by the Web server, but perhaps something has changed.
Good luck!
-----Scott.