We recently upgraded our Subversion server from 1.6 to 1.8 and since
then some of our users
our reporting problems checking out certain folders using a 1.8
client. The issues occur whether using TortoiseSVN 1.8.x or any 1.8
CLI client on Windows/Cygwin/Linux.
We have verified that these operations work with 1.4, 1.6 and 1.7 svn clients.
The errors we are seeing during a clean checkout from the client side
look like this depending
on the folder checked out:
svn: E175002: GET request failed: 400 Bad request
There is no corresponding error in the Apache HTTP logs.
svn: E200014: Checksum mismatch for <file>
expected: 4b4ef9e3432aa84aed190457b68c01ad
actual: 863b9f52f352a5cb20298ef0eecb9e97
In this case the server logs have this:
[Tue May 12 12:13:05 2015] [error] [client 153.65.184.225] Unable to
deliver content. [500, #0]
[Tue May 12 12:13:05 2015] [error] [client 153.65.184.225] Could not
write data to filter. [500, #175002]
The checksum mismatch error can be worked around by going to the root
of the WC and
doing:
svn update --set-depth empty
svn update --set-depth infinity
but it would be nice to have this fixed without having to jump through
these hoops.
Downgrading subversion to 1.6 fixes the issue, but without going into
too many details we will need to upgrade to 1.8 eventually.
I've done some searching and although I've seen these issues posted, I
haven't seen any solution that fixes our problem, including setting
http-chunked-requests = no.
Our environment looks like this:
OS: SLES 11 SP3
Subversion: 1.8.13
Server version: Apache/2.2.12 (Linux/SUSE)
APR 1.3.3, APR-Util 1.3.4
I would appreciate any feedback, even if it's something like "Hey
dumbass, did you try X?"
I can also provide abridged config files as well or any more
information need to fix the problem.
Thanks.
Clay Porter
