Hi all, I'm trying to use Squid (3.5.27, in a docker container) as a non-caching reverse proxy with http inbound and https outbound, to support an application that requires a proxy for internet access but does not allow proxy configuration (and I do not have access to the application's host machine). Ideally the squid proxy itself would not have a tls cert, since inbound traffic would be http, and I would like to add headers.
What keeps stopping me is that I also need to support a parent forward proxy, which itself may support http or https inbound. I've tried the various examples here <https://wiki.squid-cache.org/SquidFaq/ReverseProxy>, but I'm struggling to "flip" the proxy direction - receive the request as a reverse proxy, configure the outbound request appropriately, and then send it on *via* the parent proxy. I'm not sure if cache_peers can be "chained" like this, or if they can't, how I can configure the single cache_peer so that proxied https works correctly. This is my first foray into complex proxy configuration, so I'm not sure whether I'm close or completely off base. Can provide more details or try any suggestions. Thanks! -- *Joel Howard* Software Technical Lead jhow...@tetrascience.com | (330) 209-5779 [image: Logo Description automatically generated] <http://www.tetrascience.com> <https://www.linkedin.com/company/tetrascience> <https://twitter.com/TetraScience> <https://www.youtube.com/channel/UCxAIGW2oF5jgJ062pax98UQ>
_______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
