Re: APT do not work with Squid as a proxy because of pipelining default
- To: debian-devel@lists.debian.org
- Subject: Re: APT do not work with Squid as a proxy because of pipelining default
- From: Roger Lynn <Roger@rilynn.me.uk>
- Date: Wed, 19 May 2010 00:05:18 +0100
- Message-id: <[🔎] 4BF31D2E.7020209@rilynn.me.uk>
- In-reply-to: <eLkpQ-5eC-7@gated-at.bofh.it>
- References: <eL13Q-1VN-1@gated-at.bofh.it> <eL2CC-4ij-15@gated-at.bofh.it> <eLgmf-7BR-11@gated-at.bofh.it> <eLiR4-2Tj-5@gated-at.bofh.it> <eLkpQ-5eC-7@gated-at.bofh.it>
On 18/05/10 03:10, Robert Collins wrote:
> Given that pipelining is broken by design, that the HTTP WG has
> increased the number of concurrent connections that are recommended,
> and removed the upper limit - no. I don't think that disabling
> pipelining hurts anyone - just use a couple more concurrent
> connections.
But apt has been using pipelining for years. Why has this only just
become a problem? Not all proxies dislike pipelining - Polipo is an
example of one that works well with it. It also works with at least some
proprietary/commercial proxies too. And if transparent proxies can't
cope with pipelining then they're broken and not very transparent. I
think if this was a significant problem it would have been noticed a
long time ago. However disabling pipelining if a proxy is configured is
probably a good idea to ensure compatibility and is commonly done in
browsers, but it's not necessary for direct connections.
Roger
Reply to: