Michael Bowe wrote:
-----Original Message-----
From: Matthew Morgan [mailto:atcs.matthew@xxxxxxxxx]
Sent: Saturday, 14 November 2009 7:59 AM
To: Squid Users
Subject: Re: Re: ubuntu apt-get update 404
Apparently I only get the dropped .bz2 extensions when using squid
transparently, which is how our network is set up. If I manually
specify http_proxy on my workstation to point to squid directly, I
don't
have any problems with apt-get update. Has anyone ever heard of this?
Here's my updated squid config (this is 3.0-STABLE20, btw).
I've been having perhaps related problems with Debian servers behind Squid
3.1.0.14 TPROXY
I am not getting 404's but am intermittently seeing "invalid reply header"
errors. eg :
Failed to fetch
http://backports.org/debian/dists/etch-backports/main/binary-amd64/Packages.
gz The HTTP server sent an invalid reply header
Err http://security.debian.org lenny/updates Release.gpg
The HTTP server sent an invalid reply header [IP: 150.203.164.38 80]
W: Failed to fetch
http://security.debian.org/dists/lenny/updates/Release.gpg The HTTP server
sent an invalid reply header [IP: 150.203.164.38 80]
As you say, if I specify HTTP_PROXY= to go direct to the cache rather than
transparent then all works fine
Michael.
I wonder. Is that actually 3.1.0.14 direct to origin? or perhapse going
through some older sub-cache?
Are the two of you able to provide me with "tcpdump -s0" traces of the
data between apt and squid please? particularly for the transparent mode
problems.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20
Current Beta Squid 3.1.0.14
