[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Can't co svn.collab.net from Windows clients

From: Blair Zajac <blair_at_orcaware.com>
Date: 2003-11-27 19:44:40 CET

[cc' dev@subversion]

Juanma Barranquero wrote:
> On Wed, 26 Nov 2003 19:27:24 -0800
> Blair Zajac <blair@orcaware.com> wrote:
> > I'm getting the exact same error from both the svn.exe and the
> > TortoiseSVN client when trying to check out
> >
> > http://svn.collab.net/repos/svn/trunk/doc/book/book
> I'm doing "svn update" daily from that server on a W2K machine (I'm
> using the prebuilt 0.33.1 binaries).
> > Here's what I'm seeing:
> >
> > $ svn co http://svn.collab.net/repos/svn/trunk/doc/book/book svn-book-simple
> > svn: RA layer request failed
> > svn: REPORT request failed on '/repos/svn/!svn/vcc/default'
> > svn: REPORT of '/repos/svn/!svn/vcc/default': 400 Bad Request (http://svn.collab.net)
> >
> > I can check out code from my own 0.33.1 Subversion server running
> > on RedHat 9 just fine. And I can check this collab.net URL on my
> > RedHat box too, so it looks like some odd interaction between the
> > collab.net server and Windows. This check out worked several days
> > ago.
> Excuse the question but, are you sure you don't have a proxy problem? I
> access through https://... because our proxy is quite picky (on http://
> it was blocking the required WebDAV/DeltaV methods).

Good point, didn't think of that.

Several days ago I was either at work or at home with no proxy. Now,
I'm on vacation using Sprint's PCS wireless internet access and they
must have a proxy in the way. Switching to port 81 got the update to
work just fine.


Blair Zajac <blair@orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 27 19:45:53 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.