[squid-users] Have issue with "https_port ssl-bump intercept"
pius
piuschungath at gmail.com
Mon Aug 13 08:32:03 UTC 2018
Hi,
Thanks for the reply. I haven't got access to log on weekend, sorry about
the late reply.
I google about this error. I got some answer like connect message is in
plain text and squid is expecting a TCP communication and it gets rejected
in lower level before getting to step 2. I am not sure that maybe my issue.
Please check logs and let me know what I am doing wrong
####### curl #####
* About to connect() to proxy 10.222.17.106 port 3130 (#0)
* Trying 10.222.17.106...
* Connected to 10.222.17.106 (10.222.17.106) port 3130 (#0)
* Establish HTTP proxy tunnel to www.google.com:443
> CONNECT www.google.com:443 HTTP/1.1
> Host: www.google.com:443
> User-Agent: curl/7.29.0
> Proxy-Connection: Keep-Alive
>
* Recv failure: Connection reset by peer
* Received HTTP code 0 from proxy after CONNECT
* Connection #0 to host 10.222.17.106 left intact
curl: (56) Recv failure: Connection reset by peer
###### access.log ####
1534148669.183 0 10.222.25.60 TCP_DENIED/200 0 CONNECT
10.222.17.106:3130 - HIER_NONE/- -
############
--
Sent from: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
More information about the squid-users
mailing list