Fine, at least some progress. Now you should upgrade your squid and verify, that http forwarding still works.
http://wiki.squid-cache.org/Features/BumpSslServerFirst is based on squid 3.3 But you have 3.1 You should not use any other wiki/info as directly mentioned here in the forum. Because the developers are here from time to time, too. So you will get up-to-date info. And from most knowledgable source. As a step-by-step procedure, I would first to try to set up explicit (non-transparent) SSL-proxy with squid, to be accessed because of definition in the browsers proxy settings. So it would mean, the google-proxy must be SSL-capable first and only. This should be the simplest possible https-proxy config. In case, then you setup a proxy.pac for the browser, this would be a simple, alternate solution regarding splitting up the traffic to different squids. -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/peer-cache-question-tp4659419p4659499.html Sent from the Squid - Users mailing list archive at Nabble.com.
