| 2013-01-01 19:22:54 |
Jim Salter |
description |
Not sure why, but squid-deb-proxy ALWAYS thinks that any package or list from dl.google.com is a miss. I've had squid-deb-proxy installed and working on the machine below for quite a while now, and have dl.google.com added to /etc/squid-deb-proxy/mirror-dstdomain.acl.
I noticed today that installing Chrome on a new machine was going at internet speeds, not LAN speeds, and investigated - TL;DR, squid-deb-proxy always thinks anything from dl.google.com is a miss:
jrs@locutus:~$ sudo grep google /var/log/squid-deb-proxy/access.log | wc -l
49
jrs@locutus:~$ sudo grep google /var/log/squid-deb-proxy/access.log | grep TCP_MISS | wc -l
49
I don't know if this is a "bug" with squid-deb-proxy or a "bug" with Google's server... but it sucks. =) |
Not sure why, but squid-deb-proxy ALWAYS thinks that any package or list from dl.google.com is a miss. I've had squid-deb-proxy installed and working on the machine below for quite a while now, and have dl.google.com added to /etc/squid-deb-proxy/mirror-dstdomain.acl.
I noticed today that installing Chrome on a new machine was going at internet speeds, not LAN speeds, and investigated - TL;DR, squid-deb-proxy always thinks anything from dl.google.com is a miss:
me@locutus:~$ sudo grep google /var/log/squid-deb-proxy/access.log | wc -l
49
me@locutus:~$ sudo grep google /var/log/squid-deb-proxy/access.log | grep TCP_MISS | wc -l
49
I don't know if this is a "bug" with squid-deb-proxy or a "bug" with Google's server... but it sucks. =) |
|
