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 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bf31d2e.7020...@rilynn.me.uk
