invalid range access during branch over http

Last 43 packets from the stream.

Looking at the ethereal dump, I see that we make a request with

Range: bytes=0-853,974-1092

And the response seems to be multipart, and have:
Content-Type: multipart/byteranges; boundary="dFAeio52rA5c5-/w6C'c"

--dFAeio52rA5c5-/w6C'c

Content-Type: text/plain; charset=UTF-8

Content-Range: bytes 0-853/1093

Now, the actual content is gzipped binary data, so I don't know why it is return text/plain; charset=UTF-8, but the important bit is that there isn't a second chunk which contains:

--dFAeio52rA5c5-/w6C'c
Content-Type: text/plain; charset=UTF-8
Content-Range: bytes 974-1092/1093

I can confirm that bazaar-vcs.org is capable of returning the whole thing. So it seems like your proxy is restricting content to a single returned chunk, rather than returning the full request.

This seems to be a limitation of your proxy. Though it could be fixed in a similar way to bug 62029. Basically, we could detect that your http route is incapable of supporting a multi-range request, and change our requests to always be a single range, even though it is wasteful.

A fix is available in the associated bzr.urllib.keepalive branch.

New target 0.13