Tom Rushworth wrote:
 > So I tried it with svn 1.1.3, and got:
 >
 > @ svn co http://squeak.hpl.hp.com/svn/squeak/trunk/platforms
 > subversion/libsvn_ra_dav/util.c:670: (apr_err=175002)
 > svn: REPORT request failed on '/svn/squeak/!svn/vcc/default'
 > subversion/libsvn_ra_dav/util.c:294: (apr_err=175002)
 > svn: REPORT of '/svn/squeak/!svn/vcc/default': 400 Bad Request
 > (http://squeak.hpl.hp.com)
 >
 > My svn installation works as far as the test described in the
 > installation ReadME:
 >    svn cat http://svn.collab.net/repos/svn/trunk/README
 > I'm running on a Mac, OS X 10.3, behind a NATted firewall, if that makes
 > any difference.

We were seeing similar symptoms here (using svn 1.1.3 on Fedora Core 1, 
behind a Squid 2.5.STABLE6 proxy). It turned out that our proxy was not 
configured to handle the WebDAV requests svn uses to access the 
repository [see http://subversion.tigris.org/faq.html#proxy].

Our workaround is to route the svn connections through a Socks5 proxy:
socksify svn co http://squeak.hpl.hp.com/svn/squeak/trunk
works fine (using the Dante Socks library from http://www.inet.no/dante/).

It seems that e.g.
svn cat http://squeak.hpl.hp.com/svn/squeak/trunk/platforms/unix/README
works if using the Squid HTTP proxy, while 'svn co ...' and 'svn update' 
do not.


- Wolfgang