RE: Update causes "400 Bad request"

Florian Pose wrote:
> 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 - html/xml)

[...]

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

I'm no expert, but could it be the Squid proxy blocking
MIME content types?

Considering that explicitly blocking text/xml would be
a pretty extreme measure, Squid may be configured to
only allow certain types (like text/html, image/gif,
text/plain) and disallow all others?

It's worth a look, anyway.

-- 
Robert Hunter
*****************************************************************************
This communication, including any attachments, is confidential.
If you are not the intended recipient, you should not read it
- please contact me immediately, destroy it, and do not copy
or use any part of this communication or disclose anything about it,
Thank you.
Please note that this communication does not designate an information system
for the purposes of the Electronic Transactions Act 2002
******************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org