Thanks a lot for your Answer Amos, My mistake, I have to use intercept and use squid as transparent proxy (I was lazy to setup a router, setup transparent proxy m/c. I should do it now.). I have changed the configuration to use http_port instead of https_port and then removed "intercept". this works outside docker. 2nd step is to try this inside docker. Thanks again for your help. Amos Jeffries wrote > You are connecting the curl and browser to port 8080. Which is > configured to *only* receive traffic from the OS NAT system (intercept > flag). > > Remove the "intercept" flag from Squid if you are going to connect to > that port with clients, or duplicate the ssl-bump configuration on the > port 8080 line. > > If you are only doing this for "testing". Then please stop. Test what is > actually going to be used - in the *way* that it is actually going to be > used. As if your tester was one of the real clients. > > HTTP (and HTTPS) are remarkably complicated these days. Testing with a > completely different type of traffic than you expect to occur normally, > is not going to get you anywhere near a working system. > > Amos > > _______________________________________________ > squid-users mailing list > squid-users@.squid-cache > http://lists.squid-cache.org/listinfo/squid-users -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Error-negotiating-SSL-connection-on-FD-12-Success-tp4671090p4671149.html Sent from the Squid - Users mailing list archive at Nabble.com. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
