Hi Alan, Thanks for the info. Yeah, configuring ATS to remap URLs from HTTP to HTTPS could work. Is it possible to do this only on a particular port? So I would then have a port which does not remap, and a port which does, in essence simulating my use case.
So it possible to write a remap rule from http://* to https://* for requests received at a port XXXX? Thanks, Vikram On Tuesday, December 10, 2013 3:46 PM, Alan M. Carroll <a...@network-geographics.com> wrote: I don't think you can do this in ATS currently. Do you need SSL between the curl host and ATS? If not, you could configure ATS to remap URLs from HTTP to HTTPS to get an SSL connection from ATS to the origin server. Also, if you are using curl, you could set ATS up to use forward proxy on an SSL port and then use --proxy on the curl command. That would give you SSL on both connections. Tuesday, December 10, 2013, 3:05:52 PM, you wrote: > Hi, > I want to set up the apache traffic server in forward proxy mode where it > caches all data fetched through it. In the default set up, caching SSL is > pointless as ATS does not see the data flowing through it. > I am trying to figure out if it is possible to configure SSL termination for > the forward proxy mode so that ATS can see the data flowing through it for > https requests too so that cahcing is possible. Note that urls are fetched > though curl with the "-k/--insecure" option turned on so certificate > validation is not an issue, and any self signed certificate will do. No > spoofing of the end server is necessary. > Has anyone got ATS running in this setup? Or would it need code > modification/special plugins to do this?
