Re: [squid-users] cache_peer causes 'https proxy request speaking HTTP to HTTPS port' error

From: Stephan Hügel <urschrei_at_gmail.com>
Date: Thu, 26 May 2011 17:53:30 +0100

> Squid logs the peer selection details at debug level 44,3. Its a bit obtuse
> in most releases so far.

Attempting to connect to https://www.domain.com:
2011/05/26 17:45:15.292| peerSelect: CONNECT
2011/05/26 17:45:15.292| peerSelectFoo: 'CONNECT www9.respondingtolife.com'
2011/05/26 17:45:15.292| peerCheckNeverDirectDone: 0
2011/05/26 17:45:15.292| peerSelectFoo: 'CONNECT www9.respondingtolife.com'
2011/05/26 17:45:15.292| peerSelectFoo: direct = DIRECT_MAYBE

After altering the dstdomain directive to www.foo.com, and attempting
to connect to http://www.foo.com:
2011/05/26 17:47:37.122| peerSelect: http://www.foo.com/
2011/05/26 17:47:37.122| peerSelectFoo: 'GET www.foo.com'
2011/05/26 17:47:37.122| peerCheckNeverDirectDone: 1
2011/05/26 17:47:37.122| peerSelectFoo: 'GET www.foo.com'
2011/05/26 17:47:37.122| peerSelectFoo: direct = DIRECT_NO
2011/05/26 17:47:37.122| peerSelectIcpPing: http://www.foo.com/
2011/05/26 17:47:37.122| peerSelectIcpPing: counted 0 neighbors
2011/05/26 17:47:37.122| peerGetSomeParent: GET www.foo.com
2011/05/26 17:47:37.122| peerSelect: FIRST_UP_PARENT/[correct peer IP
from cache_peer directive]
2011/05/26 17:47:37.122| peerSelectCallback: http://www.foo.com/
2011/05/26 17:47:37.123| peerSelect: http://[correct peer
IP]:443/squid-internal-periodic/store_digest

-- 
steph
Received on Thu May 26 2011 - 16:53:37 MDT

This archive was generated by hypermail 2.2.0 : Thu May 26 2011 - 12:00:03 MDT