2017-04-01 8:33 GMT-04:00 James McCoy <james...@debian.org>: > Given that there's an easy workaround (set http-chunked-requests to > off) I'm lowering the severity of the bug. >
u lowering, but this issue afected many users in the internet! but due are not close to the distributions (thei'r not familiar to send bugs) its only reported at sites like stackoverflow or similar.. i reported to debian due its the most easy place to do, but its tedious explainthat its a real problem (4 emails to u understand and also give u infraestructure to test) and then "lowering" the priority! that's wahy today the tiny distributions are growing and big distribution getdown in quality IF U NEVER USE SVN HOW U CAN TELL ME TO ME A FRECUENTY USER OF SVN WHAT ARE ISSUE OR NOT!? its ironic and tedious! now i understand why its so many users migrating to alpine and similar > > 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 >
