Control: severity -1 normal On Wed, Mar 29, 2017 at 08:21:23AM -0400, PICCORO McKAY Lenz wrote: > 2017-03-28 23:04 GMT-04:00 James McCoy <james...@debian.org>: > > This discussion is specifically talking about when a 411 status is > returned, not a 413. > > the document only cited 411 error as example, could not cover all the cases > due > there are more, if u understand how to work http 1.1 vs other http 1.X and 2
You're right that it documented the known problems. However, given that 1.8.1 was published almost 4 years ago, I'd expect that common problems would have come up. Given that there's an easy workaround (set http-chunked-requests to off) I'm lowering the severity of the bug. I agree that the general setup you describe of having a proxy is common, but I think the particular proxy or proxy configuration you happen to be interacting with is rather broken. Making it more robust to standard HTTP headers is a much better fix than disabling auto-detection of the correct http-chunked-requests setting for a broader class of users. > well ist not working, i provide not only one, i provide two urls where u come > and get to test.. once with svn 1.6.12 and once with svn 1.7.0 rc1 and theres > no work > > seend to you in private mail: The IP URL is just plain broken. All I get is a 500 response, no matter how I try to run svn. The name-based URL does respond when http-chunked-requests is disabled, but breaks when auto-detection is enabled. I'll discuss this with upstream to see if there's something better than can be done here. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
