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

Re: Unexpected HTTP status 400 'Bad request'.

From: Chris Capon <ttabyss_at_gmail.com>
Date: Tue, 8 Dec 2015 16:09:06 -0500

On 2015-12-08 09:09, Bert Huijben wrote:
> Are you using some kind of (caching) proxy server when you connect to
> the server? You are focusing your search to a disk problem (probably
> caused by hints on this list), while you are trying to determine what
> causes a 'bad HTTP request' error. Bad requests on these urls may be
> caused by sending bad header values... I've seen those before when
> using nginx as proxy with a too strict caching policy. Bert
No proxy server. As I say, to eliminate the possibility, I'm even
connecting from a terminal on the subversion server and trying it from
there. Going through apache2, it fails, going directly through file
access succeeds.

But the confusing thing is that the error doesn't happen with the
initial connection, it happens part way through after several files have
transferred successfully. And it seems inconsistent. It doesn't always
fail on the same file.

What I don't know is how to diagnose the communications through apache
and to the subversion server. No error messages appear in any of the
apache2 logs nor the subversion log. So where is the error happening?
Received on 2015-12-08 22:09:15 CET

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.