[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

SVN Failure: Could not read response body

From: Mark Moore <mark.moore_at_notlimited.com>
Date: 2007-01-22 04:19:07 CET

Hello,

 

I've been using SVN for a while, and I'm noticing a problem that appears to
be a subversion server issue. Namely on *large* initial updates, the client
reports "Could not read response body: Secure connection truncated
(https://<svn-server-url>)".

 

This seems to be a frequently seen problem from the large number of hits I
find if I Google the "Could not read response body" phrase, but I haven't
been able to find anything in the SVN issue tracking system, and I haven't
been able to find a clear work around. Anyone out there have any links or
advice?

 

I believe we're using an Apache SVN server, and we're definitely using a
TortoiseSVN client on Windows XP Pro (if that matters). The symptom is that
usually, the initial update will puke on its shirt after a couple 100M of
download. Usually, I can just re-issue the update command, and it will pick
up where it left off and finish up after 2-3 restarts. Once the initial
update completes successfully, I have not experienced any failures.

 

What has me stumped now is that it is continuously failing and I can't
complete the initial update. Any help would be greatly appreciated.

 

-Mark

 
Received on Mon Jan 22 04:20:28 2007

This is an archived mail posted to the Subversion Users mailing list.