On 09.01.2014 17:09, Mojca Miklavec wrote: > I'm unable to reproduce the faulty behaviour if I do a checkout from > the same network where the server is located, no matter what I try > (upgrading SVN client doesn't "help" triggering the error). Philip > also said that he had no problem doing a checkout with client version > 1.8.5 or 1.7.
This confirms my suspicion that the error is triggered by some part of the network infrastructure between your server and the outside world. That's why I asked if there is a load-balancer involved. It could also be caused by some kind of transparent proxy, or even a packet analyzer. I doubt that your server is open to the world without some kind of security measures in place. To be clear, I'm not saying that any of these things are configured incorrectly; only that they may be interacting with Subversion in a way that we don't handle well. One of the major differences between 1.7 (which works) and 1.8 (which fails) is that we try to work around issues with non-standard behaviour of certain "transparent" (sic) proxies; and we can't claim to have covered all the possibilities. I can't see a way to figure out what's going on without help from your network admins; we need some insight into why the connection is being reset on the server side, and analyzing the TCP stream on the client can't tell us that. BTW, if you think it'd help to try a live debugging session, I'm only about an hour's drive away from IJS. -- Brane -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. br...@wandisco.com
