Am Sonntag, 23. April 2017, 18:03:25 CEST schrieb Amos Jeffries: > You appear not to be using curl correctly. > > Test #1 and #3 show that curl is probably sending the https:// requests > through port 8080 on your proxy as a CONNECT request. Check that in your > Squid log to confirm. I wasn't aware of that thx, but nevertheless the problem still exists curl -x 'proxy:8443' https://www.google.de curl: (56) Recv failure: Connection reset by peer # no log entry curl -x 'proxy:8443' http://www.google.de curl: (56) Recv failure: Connection reset by peer # no log entry curl -x 'proxy:8080' http://www.google.de # no output [23/Apr/2017:19:28:53 +0000] "GET http://www.google.de/ HTTP/1.1" 301 206 "-" "curl/7.47.0" TCP_DENIED:HIER_NONE curl -x 'proxy:8080' https://www.google.de # works [23/Apr/2017:19:29:27 +0000] "CONNECT www.google.de:443 HTTP/1.1" 200 15157 "-" "curl/7.47.0" TCP_TUNNEL:HIER_DIRECT The corresponding tcpdumps are here to be found: https://nopaste.me/view/ 1e07d687 _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
