[squid-users] intercept squid 3.5.1, http://mail.ru

Yuri Voinov yvoinov at gmail.com
Sat Feb 14 21:48:54 UTC 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I can to reproduce this with trace at Monday. My users uses that.

15.02.15 3:46, Amos Jeffries пишет:
> On 15/02/2015 9:26 a.m., Jason Haar wrote:
>> But this is just a hack around a problem isn't it?
> 
> Yes.
> 
>> ie why can't squid successfully intercept 20M+ transfers from
>> this website?
> 
> Well, Squid *is* intercepting them. Its what happens after that is 
> going wrong.
> 
>> I guess it's working for 1byte-10M transactions, so why not 20M?
> 
> Indeed. Lets look closer...
> 
> 
>> 1423851413.570    228 192.168.100.111 TAG_NONE/200 0 CONNECT 
>> 217.69.141.150:443 - ORIGINAL_DST/217.69.141.150 -
> 
> Squid receives a CONNECT, bumps it...
> 
> 
>> 1423851413.670     81 192.168.100.111 TCP_MISS/410 291 POST 
>> https://jim24.mail.ru/helper? - ORIGINAL_DST/217.69.141.150 
>> text/html
> 
> 
> .. inside is a POST to "jim24.mail.ru:443"
> 
> Squid delivers that to the server the CONNECT was going to 
> (217.69.141.150:443).
> 
> The server responds "410 Gone".
> 
> 
> A debug_options 11,2 trace might provide more insight.
> 
> 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

iQEcBAEBAgAGBQJU38LGAAoJENNXIZxhPexGbJcH/1LYvgYWwlczMjSTOSgXIkDb
UjNTDUGMO5b4MnJbGKE+4RYDle6zImYFXvw7hQCzfTigpJk8X6V+ZB6GhyKULjY+
+ACndtPj4WyixE2Om59Vf3iXZXv47c1rLitFSaARg8dHJh8BnAuBX1fEgeL+uhVO
oNZjq4hl5QOObixrrd9YtxiN34nL1suY0Hd8LCBcd1UuGqEqTM7Q4C0mp9GZ1Y0m
8OEQA8wUxjiES4b2b44Dv4DwwG5ulomHXZedJXMUMIiPPsmLM4ro46bdKQ+gQNj/
ouQ9t3yDnw4UJaqzy4WVZ0/hdCWkCBDmsLaD6OFYboQrZvZe5/xzfYl5kh1Q9Cs=
=fQUk
-----END PGP SIGNATURE-----


More information about the squid-users mailing list