Re: Can't connect to SVN servers via HTTP-- could not read status line: connection was closed by server

Geoff,

Thanks for your reply. I've tried the things you've suggested and already read through the stack overflow posts you listed, but I looked at them all again.

One of the comments to the last post mentioned antivirus software, which got me thinking. Among other things I uninstalled my VPN software and boom, it works now. Apparently, it was filtering out http traffic from the svn client, even though I was connected via VPN.

Weird, weird, weird, weird.

Anyway, thanks.

Conan.

On Oct 11, 2012, at 6:58 PM, Geoff Hoffman <ghoffman_at_cardinalpath.com> wrote:

> I've seen that same message before many times, but always with my own misconfigured http+mod_dav+dav_svn setup, never with someone else's working repo.
>
> Try https instead of http?
> Check proxy settings?
>
> Check here for more possibilities:
> http://stackoverflow.com/questions/613149/svn-could-not-read-status-line-connection-was-closed-by-server
> http://stackoverflow.com/questions/732681/tortoisesvn-couldnt-read-status-line-in-vm
> http://stackoverflow.com/questions/783186/what-does-the-subversion-error-could-not-read-status-line-mean
>
> Also, what version of svn are you running?
> Did you build it or install the binary?
> What platform?
> Are you using a 3rd party client or command line?
>
>
>
>
> On Thu, Oct 11, 2012 at 3:22 PM, Heiselt, Conan <conan.heiselt_at_gmail.com> wrote:
> svn: OPTIONS of 'http://jquery-ui.googlecode.com/svn/trunk': Could not read status line
>
>
>
>
>
> Connect with us on twitter, google+, facebook, or linkedin.
> Catch our next training in Houston Oct 8 - 12, Berkeley Oct 22 - 26, Seattle Oct 29 - Nov 2, Phoenix Nov 12 - 16 or See All.
>
>
>
>
>
>
>
>
> This email, including any attachments, is for the sole use of the intended recipient and may contain confidential information. If you are not the intended recipient, please immediately notify us by reply email or by telephone, delete this email and destroy any copies. Thank you.
>
>
>
>
>
Received on 2012-10-12 18:29:59 CEST