On 1/9/14, 11:19 AM, Branko Čibej wrote: > To be clear, I'm not saying that any of these things are configured > incorrectly; only that they may be interacting with Subversion in a way that > we > don't handle well. One of the major differences between 1.7 (which works) and > 1.8 (which fails) is that we try to work around issues with non-standard > behaviour of certain "transparent" (sic) proxies; and we can't claim to have > covered all the possibilities.
Actually we know we haven't covered all possibilities. Had someone a while back that had mod_security setup in such a way that it was rejecting some request methods (think it was POST) without Content-Length (thus breaking chunked requests). The behavior didn't fail for the OPTION requests so our probe to try and work around transparent proxies failed. But I'm not sure what this thread would really have to do with chunked requests, since the problem seems to be pipelining which as far as I know we don't have any workarounds for. We can rule out the chunked requests by disabling it by adding this to the command line --config-option servers:global:http-chunked-requests=no and seeing if it changes anything. But I really doubt it based on what I've seen on this thread. More details on what Branko is talking about and the config option I mentioned here: https://subversion.apache.org/docs/release-notes/1.8.html#411-length-required
