Hello! I’m running ATS 4.1.2 on Ubuntu 12.04.3 as a forward proxy for the caching purposes. I’m using policy based routing in my Juniper SSG 140 (Screen OS) to route traffic to my ATS on port 8080. As of now I only have traffic destined for port 80 TCP hitting the ATS, but I would like to also direct SSL traffic there as well, but I am running into a snag. If I manually configure the ATS as an HTTP & HTTPS proxy on my Mac, a linux box or an iOS device, both HTTP and HTTPS traffic have no issues being proxied through the ATS, and all downloads - even iOS and Mac App store downloads cache just fine (which is a major point of this ATS setup). However, if I configure in my SSG 140 to also route both port 80 and port 443 destined traffic to the ATS (so that manual configuration is not required on devices) no SSL traffic will work anymore. Web browsers will say a secure connection could not be established. What can be done to replicate the behaviors being performed when an HTTPS proxy is manually defined on a device using the routing features in the SSG140, so that devices require no configuration once on the network. Thank you for your hard work making the Internet faster!
-- Matt Peterman 614.905.0099 [email protected]
