I cited why must be set for 1.8 and q.9 until 1.10 released: Users who wish to avoid the additional request may set that option to yes or no in order to short-circuit the additional request and avoid making it.
later we have: The Serf-based HTTP access library would use chunked transfer encoding for most requests. When themod_dav_svn Subversion server is fronted by a proxy or reverse proxy its common that well made configuration are a light webserver for front request and specialiced webserver for each specific task, in this case, apache2 for subversion.. so obviously u dont have how to test, and package dont have any of these guaranties.. I NOTE MANY SIMILAR CASES UNRESOLVED in large amount of bugs in debian bug list for subversion package.. so then please leave aside the selft defensive excuses and please fix the package.. Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com 2017-03-28 22:28 GMT-04:00 James McCoy <james...@debian.org>: > On Tue, Mar 28, 2017 at 07:34:46PM -0400, PICCORO McKAY Lenz wrote: > > Package: subversion > > Version: 1.8.10-6+deb8u4 > > Severity: grave > > Justification: renders package unusable > > > > Dear Maintainer,the current package in debian are broken > > i upgrade clients to jeesie > > and now could'n chekout working copies from external networks, only > > internal local network > > > > but when i conpiled my own package, but version 1.8.0 im able to > > chekout from any svn of any version > > > > * What led up to the situation? > > I used debian wheeze (clients) and squeeze (servers) > > and then upgrade/install jeesie on clients, but servers leave intact > > due great performance > > (note that some tests on wheeze does not report good performance, no > > hardware update will) > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > svn co http://<ip>/svn/project1 > > * What was the outcome of this action? > > Unable to connect to a repository at URL 'http://<ip>/svn/project1' > > Unexpected HTTP status 413 'Request Entity Too Large' on '/svn/project1' > > You suggest that setting "http-chunked-requests = no" fixes this, when > the error in the release notes is a 411, not a 413. Are you sure that > has an impact? Without a server to test against, I can't investigate > the problem. > > As far as changing the config, the default value is to auto-detect > whether chunked requests are supported. If your specific proxy is > broken, then I would suggest following the directions in the release > notes and setting the config that's needed for you _just_ for that > server. > > Cheers, > -- > James > GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB >
