On 7/10/19 7:44 PM, Arunabha Saha wrote: >> The client will attempt to open a TLS/TCP connection to the origin >> server. Your router (or some such) will redirect client TLS/TCP bytes to >> your Squid's https_port. If configured correctly, Squid will accept that >> TCP connection and wrap/forward it into/inside an HTTP CONNECT tunnel >> through the corporate proxy. > i don't see squid > wrap the connection to parent proxy in a HTTP CONNECT tunnel. > User ----->Squid(Transparent Proxy)--------->Parent Proxy------>Internet. > I need to see a CONNECT tunnel between Squid(Transparent Proxy) > and Parent Proxy but I don't. Based on another thread, Is this > something that works only starting squid 4.X. I do not remember for sure, but you may need a development version of Squid (future v5) or an unofficial patch to forward intercepted tunnels to a cache peer. If SslBump-related peering support is indeed required to support such forwarding, then please see this seemingly unrelated bug report for more details and options: https://bugs.squid-cache.org/show_bug.cgi?id=4968 Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users