[squid-users] Is it possible to send the connection, starting with the CONNECT, to cache-peer?
Yuri Voinov
yvoinov at gmail.com
Tue Sep 22 15:56:25 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
- ---------
CONNECT www.torproject.org:443 HTTP/1.1
Host: www.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 21:54:01.269 kid1| peer_select.cc(258) peerSelectDnsPaths:
Find IP destination for: www.torproject.org:443' via www.torproject.org
2015/09/22 21:54:01.269 kid1| peer_select.cc(280) peerSelectDnsPaths:
Found sources for 'www.torproject.org:443'
2015/09/22 21:54:01.269 kid1| peer_select.cc(281) peerSelectDnsPaths:
always_direct = DENIED
2015/09/22 21:54:01.269 kid1| peer_select.cc(282) peerSelectDnsPaths:
never_direct = DENIED
2015/09/22 21:54:01.269 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=0.0.0.0
remote=86.59.30.40:443 flags=1
2015/09/22 21:54:01.269 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=0.0.0.0
remote=93.95.227.222:443 flags=1
2015/09/22 21:54:01.269 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=0.0.0.0
remote=154.35.132.70:443 flags=1
2015/09/22 21:54:01.269 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=0.0.0.0
remote=82.195.75.101:443 flags=1
2015/09/22 21:54:01.269 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=[::]
remote=[2001:858:2:2:aabb:0:563b:1e28]:443 flags=1
2015/09/22 21:54:01.269 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=[::]
remote=[2001:41b8:202:deb:213:21ff:fe20:1426]:443 flags=1
2015/09/22 21:54:01.269 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=[::]
remote=[2620:0:6b0:b:1a1a:0:26e5:4810]:443 flags=1
2015/09/22 21:54:01.269 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=0.0.0.0
remote=38.229.72.16:443 flags=1
2015/09/22 21:54:01.269 kid1| peer_select.cc(295)
peerSelectDnsPaths: timedout = 0
2015/09/22 21:54:02.941 kid1| client_side.cc(2337) parseHttpRequest:
HTTP Client local=127.0.0.1:3128 remote=127.0.0.1:37495 FD 55 flags=1
2015/09/22 21:54:02.941 kid1| client_side.cc(2338) parseHttpRequest:
HTTP Client REQUEST:
- ---------
- ---------
CONNECT www.torproject.org:443 HTTP/1.1
Host: www.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 21:54:33.169 kid1| peer_select.cc(258) peerSelectDnsPaths:
Find IP destination for: www.torproject.org:443' via www.torproject.org
2015/09/22 21:54:33.169 kid1| peer_select.cc(280) peerSelectDnsPaths:
Found sources for 'www.torproject.org:443'
2015/09/22 21:54:33.169 kid1| peer_select.cc(281) peerSelectDnsPaths:
always_direct = DENIED
2015/09/22 21:54:33.169 kid1| peer_select.cc(282) peerSelectDnsPaths:
never_direct = DENIED
2015/09/22 21:54:33.170 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=0.0.0.0
remote=82.195.75.101:443 flags=1
2015/09/22 21:54:33.170 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=[::]
remote=[2001:858:2:2:aabb:0:563b:1e28]:443 flags=1
2015/09/22 21:54:33.170 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=[::]
remote=[2001:41b8:202:deb:213:21ff:fe20:1426]:443 flags=1
2015/09/22 21:54:33.170 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=[::]
remote=[2620:0:6b0:b:1a1a:0:26e5:4810]:443 flags=1
2015/09/22 21:54:33.170 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=0.0.0.0
remote=38.229.72.16:443 flags=1
2015/09/22 21:54:33.170 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=0.0.0.0
remote=86.59.30.40:443 flags=1
2015/09/22 21:54:33.170 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=0.0.0.0
remote=93.95.227.222:443 flags=1
2015/09/22 21:54:33.170 kid1| peer_select.cc(286)
peerSelectDnsPaths: DIRECT = local=0.0.0.0
remote=154.35.132.70:443 flags=1
2015/09/22 21:54:33.170 kid1| peer_select.cc(295)
peerSelectDnsPaths: timedout = 0
2015/09/22 21:54:34.377 kid1| client_side.cc(2337) parseHttpRequest:
HTTP Client local=127.0.0.1:3128 remote=127.0.0.1:37507 FD 57 flags=1
2015/09/22 21:54:34.377 kid1| client_side.cc(2338) parseHttpRequest:
HTTP Client REQUEST:
- ---------
22.09.15 3:38, Amos Jeffries пишет:
> On 22/09/2015 7:33 a.m., Yuri Voinov wrote:
>>
>> Here is access log when using IE:
>>
>> 1442863815.068 785 127.0.0.1 TCP_MISS/302 506 GET
>> http://torproject.org/ - FIRSTUP_PARENT/127.0.0.1 text/html
>> 1442863816.542 105231 127.0.0.1 TAG_NONE/200 0 CONNECT
>> www.torproject.org:443 -
HIER_DIRECT/2001:41b8:202:deb:213:21ff:fe20:1426 -
>> 1442863821.899 105210 127.0.0.1 TAG_NONE/200 0 CONNECT
>> www.torproject.org:443 -
HIER_DIRECT/2001:41b8:202:deb:213:21ff:fe20:1426 -
>>
>> and then timeout. Sometimes second connect goes to IPv4 address,
>> sometimes IPv6.
>>
>> When using Chrome/Firefox, session always starts from CONNECT 443 port.
>
> Aha. I see what you mean. The HTTP response contains no HSTS header, but
> redirects to https://. The response to the first HTTPS request then
> contains HSTS.
>
> Next details to look for is the peer-selection output and HTTP message
> details:
> debug_options ALL,0 44,2 11,2
>
>
> Amos
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWAXopAAoJENNXIZxhPexGAd8IAJ0254OwsYEa/aEhs5emfOqP
u6q7IuzlaB6VFpOL824AvguWvSKxRP2pvA37P+OtFswGRQp7k/55ID0JEOVIofmG
D3t3DxiQFJkL8PQ2nnFjzmy21Ahiix1oMACcg3EP3rHDRsv1/iwwT/LjeziVLlgd
MDiSUnnuBuNuPyAb1RVyZh20ztEf7W+EscN4LhwqIPPgpT/DzGNJkE009fjnSrnn
4nr0UF7+5FMCJxlEP0Oyj0lOW7mYAI/AjrKwe39gp9fYjk4yDXuLdw27rrzHqTlH
0/urEoJEqJpplP+Q+R63RU5JNwVvS1UlGnucoAKaV77UGtS8GpXFXw6IkOgUxqo=
=qI8b
-----END PGP SIGNATURE-----
More information about the squid-users
mailing list