Re: APT do not work with Squid as a proxy because of pipelining default
Petter Reinholdtsen <email@example.com> writes:
> I am bothered by <URL: http://bugs.debian.org/565555 >, and the fact
> that apt(-get,itude) do not work with Squid as a proxy. I would very
> much like to have apt work out of the box with Squid in Squeeze. To
> fix it one can either change Squid to work with pipelining the way APT
> uses, which the Squid maintainer and developers according to the BTS
> report is unlikely to implement any time soon, or change the default
> setting in apt for Aquire::http::Pipeline-Depth to zero (0). I've
> added a file like this in /etc/apt/apt.conf.d/ to solve it locally:
> Aquire::http::Pipeline-Depth 0;
> My question to all of you is simple. Should the APT default be
> changed or Squid be changed? Should the bug report be reassigned to
> apt or stay as a bug with Squid?
> Happy hacking,
Given that squid already has a patch, although only for newer versions,
this really seems to be a squid bug. As such it should be fixed in
squid as not only apt might trigger the problem.
That said setting the Pipeline-Depth to 0 as default or when a proxy is
configured might be advisable. Adding a apt.conf.d sniplet to the stable
apt should be a trivial change. Much simpler than fixing squid itself.
And in testing/unstable one can fix it properly or update squid to 3.0.