svn: REPORT of '/svn/!svn/vcc/default': Could not read response body: Connection reset by peer

[Nehru Sani]

Following is the error which I am getting while svn checkout. I am
using https and mod_dav_svn module. I have already tried to change
timeout both for http and SSLCache but not resolved.

And I am not using any proxy. And I have also tried to chekout on same
server and issue occurs. But same issue does not occur if I use svn
checkout file:///svn .

svn: REPORT of '/svn/!svn/vcc/default': Could not read response body:
Connection reset by peer

And following is the version info:

Apache: 2.2.10
mod_dav_svn version: 1.5.4

And I have tried both client window and linux svn client.

Regards,
~Nehru

[Yves Martin]

It is a known issue with WebDAV protocol on http(s). The probable
cause is the large size of the working copy you try to checkout.

With latest 1.6.x or 1.7.x Subversion client, you should be able to
checkout successfully.

If the problem still occurs, you should try upgrading your Subversion
version on the server-side, even if in my opinion the problem is
client-side only.

Hope this helps
Yves

[Nehru Sani]

I am not agreed !

Regards,
~Nehru

> --
> You received this message because you are subscribed to the Google Groups "Subversion SVN" group.
> To post to this group, send email to subvers...@googlegroups.com.
> To unsubscribe from this group, send email to subversion-sv...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/subversion-svn?hl=en.
>

--
"Available only for technical discussion/solution 24x7 "

[Yves Martin]

What a wonderful and positive follow-up ! Really cheerful to motivate
guys trying to help you !

So if you disagree, maybe it is because you have already tested latest
client version... or maybe your checkout is small - my personal
experience was about 1 Go working copy... or maybe something else ?
Who cares finally, you have just followed up without any additional
piece of information.

Somes advices, if you really care about your trouble:
- use tcpdump or wireshark to capture full traffic over http during
your checkout and make it accessible if you dare. Maybe someone will
get a look at it to guess what may be wrong.
- if you think (or you are sure) it comes from your network, try to do
a full checkout locally on the server itself over http/s... it may
invalidate an hypothesis

By the way, the best chance to get it fix without investigating more
is to upgrade to latest Subversion client and server versions.

In any case, come back with more details.