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

Re: Update causes "400 Bad request"

From: Florian Pose <florian_at_keenkiwi.de>
Date: 2005-02-23 17:28:26 CET

Ben Collins-Sussman wrote:
> Probably an http-proxy not recognizing the webdav REPORT request, and
> blocking it?
> Though, if that were true, the initial checkout wouldn't work either.
> Can you see the '400' error in the apache errorlog?

Ok, I got it! It was squid blocking the REPORT requests.

But now there's another strange thing: The "svn update" doesn't work
with all versions (notice the type extender at the end of the lines -


svn, Version 1.1.3 (r12730) - Built from source tarball from
subversion.tigris.org, configure --with-ssl, works fine:

1109173953.755 380 TCP_MISS/207 961 PROPFIND
http://svn.easysw.com/public/fltk/fltk/branches/branch-1.1 -
DIRECT/ text/xml
1109173954.160 403 TCP_MISS/200 885 REPORT
http://svn.easysw.com/public/fltk/fltk/!svn/vcc/default -
DIRECT/ text/xml


With svn, Version 1.1.3 (r12730) - SuSE rpm from ftp.suse.com, I get a
"400 - Bad request":

1109174055.191 384 TCP_MISS/207 961 PROPFIND
http://svn.easysw.com/public/fltk/fltk/branches/branch-1.1 -
DIRECT/ text/xml
1109174055.606 412 TCP_MISS/400 491 REPORT
http://svn.easysw.com/public/fltk/fltk/!svn/vcc/default -
DIRECT/ text/html


Seems to be, that the "text/html" makes the difference. Can someone
explain this?

Thanky for your time,

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 23 17:35:32 2005

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

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