Comment 31 for bug 198646

Indeed all the signs are that it is the proxy behaviour triggering the problem. Being an obsolete Squid release with a fix available for more than 4 years, as stated by Henrik earlier and re-confirmed by myself today, I doubt this will have much of a negative impact for new rollouts. The major reasons for rolling out proxies are to mediate between modern IP protocols and content adaptation/filtering. Capabilities the broken Squid releases are lacking, so even less likely that older versions will be installed in these critical places.

The major problem is the large legacy install base and non-proxy intermediaries cutting connections. Making bzr handle these old middleware or unexpected failures in general is a good thing.