Could not read response body: Secure connection truncated

Hi SVN users I am using svn version 1.6.11 (r934486). From time to time I have warning "Could not read response body: Secure connection truncated" on checkout from svn client and because this is only warning exit status is 0 so even if workspace is incomplete my scripts can not easily d

Re: Getting error: 'Could not read response body: Secure connection truncated'

David Aldrich wrote: My suspicion is that the error is an indication of a timeout that happens because we use per-directory authorisation in Apache. I saw an article that suggested that setting SVNPathAuthz off in httpd.conf may fix this problem. Unfortunately, we must use per-directory author

Getting error: 'Could not read response body: Secure connection truncated'

Hi During long svn operations such as checkout I am often getting the following error: 'svn: REPORT of '/subversion/myproj/!svn/vcc/default': Could not read response body: Secure connection truncated' This is on Windows XP, accessing a repo whose trunk is of size 300MB (1

Trying to rebase branch with trunk results in the error svn: REPORT of '/repos/path/!svn/vcc/default': Could not read response body: Secure connection truncated (https://ourdomain)

PORT of '/repos/path/!svn/vcc/default': Could not read response body: Secure connection truncated (https://ourdomain.com) If I specify revision numbers from the creation of the branch to trunk's current revision: $ svn merge -r 40584:40659 --non-interactive https://path/to/trunk