[squid-users] Is it possible to send the connection, starting with the CONNECT, to cache-peer?

[Amos Jeffries]

On 23/09/2015 4:39 a.m., Yuri Voinov wrote:
> 
> Ooops.  After timed out:
> 
> ---------
> CONNECT torproject.org:443 HTTP/1.1
> Host: torproject.org
> Proxy-Connection: keep-alive
> User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36
> (KHTML, like Gecko) Chrome/45.0.2454.93 Safari/537.36
> 
> 
> ----------
> 2015/09/22 22:37:55.499 kid1| peer_select.cc(258) peerSelectDnsPaths:
> Find IP destination for: torproject.org:443' via torproject.org
> 2015/09/22 22:37:55.499 kid1| peer_select.cc(280) peerSelectDnsPaths:
> Found sources for 'torproject.org:443'
> 2015/09/22 22:37:55.499 kid1| peer_select.cc(281) peerSelectDnsPaths:  
> always_direct = DENIED
> 2015/09/22 22:37:55.499 kid1| peer_select.cc(282) peerSelectDnsPaths:   
> never_direct = DENIED

I think what this is showing is that your tor_url is not matching what
we think it has been matching.

Or maybe the squid.conf you have been editing is not the one running.

This line:

>>  never_direct allow tor_url

changes the log to say "never_direct = ALLOWED" when the ACL matches.

Since it is not, I conclude that the cache_peer_access allow tor_url
line is also not matching and that is why the peer is not being used.

Amos