On Wed, Feb 8, 2012 at 15:51, Greg Stein <gstein_at_gmail.com> wrote:
> This looks like the problem where ra_serf starts out with an HTTP/1.1
> request: specifically, a chunked request. This is typically caused by
> a non-1.1 proxy in front of the server, such as nginx.
> Ideally, github would switch to a newer/better proxy such as haproxy.
Let me clarify this a bit: sticking to a 1.0 proxy obviates a huge
number of client advantages. Subversion is built using a "streaming"
model where we don't know the request length in advance. If the client
is forced to perform an HTTP/1.0 request, then it would have to shove
the entire request onto disk. Check the length, and then build a 1.0
ra_neon doesn't allow streaming like this (everything gets shoved to
disk first), which is why it can stick to 1.0 requests, and why it is
painful for the client.
Further, I don't think that HTTP/1.0 allows for gzip/deflate on the
requests, which means we have more network traffic.
So... this isn't really so much about "svn must allow for HTTP/1.0"
(yes, we'll work on it), but that github could also provide better
service overall by updating its proxy.
Received on 2012-02-08 21:59:52 CET