On 16.12.2013 18:45, Stuart MacDonald wrote: > The link I provided is *exactly* what I'm seeing, so I didn't see the > need to repeat that post. I'm in a VM, the client drops the connection > with an erroneous [FIN, ACK], just after the TCP window opens up again. > > Hm, one detail I can provide now that's not in that post: > U directory/file1 > U directory/file2 > svn: E175002: REPORT of '/svn/repos/<name>/!svn/me': Could not read > response body: connection was closed by server (http://<server>) > > I don't know what's on the server side, and may not be able to find > out, but I'll inquire. Hm, actually the network trace shows "Server: > nginx/1.0.5". Client operation is 'svn up'.
So your server is using an nginx proxy, and your 1.7 client doesn't work with it. The thing to do is to try to reproduce this with 1.8, and if it's reproducible, it's still most likely a proxy bug (nginx 1.0.5 is rather old). Reporting this to the server administrator would be the next step. -- Brane -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. br...@wandisco.com
