| Hi Amos, Just to get back to this, the conclusion is that https_port does not support ssl-bump of requests passing through CONNECT. I’ll terminate the TLS connection in front of squid through a load balancer and use http_port, which works fine. Thank you! On 4 Mar 2021, at 14:21, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: On 5/03/21 1:39 am, Niels Hofmans wrote: Hi Amos, https_port simply means TLS is the transport protocol. The transport is terminated at the proxy. There are many permutations of what is being done inside that TLS. So no http_port does not require "ssl-bump". Squid does not support TLS-inside-TLS encryption layering. Which is why "ssl-bump" only works for "intercept" or "tproxy" modes on that port directive. http_port 0.0.0.0:3128 Which means your NAT systems have no records of port 443 being diverted to port 3129. Command to reproduce: Correct test command for "https_port 3129 intercept ssl-bump" is: curl --cacert /etc/squid/ssl/squid.crt -vvv \ -X POST --data 'foo' https://ironpeak.be/ This verifies that the system is diverting traffic to the proxy, the proxy is the TLS agent for those connections, and that connectivity through the proxy is working. TLS failure to verify the cert(s) indicate the proxy is not being reached. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users |
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
