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?
