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

FW: Locks return "Bad Request"

From: Joel Low <joel_at_joelsplace.sg>
Date: 2007-05-05 14:37:20 CEST


I have not gotten any response -- would it be more appropriate if I send
this to dev instead?


-----Original Message-----
From: Joel Low [mailto:joel@joelsplace.sg]
Sent: 30 April 2007 6:08 PM
To: 'users@subversion.tigris.org'
Subject: Locks return "Bad Request"


I'm using Apache 2.2.4 and SVN 1.4.3, with the TortoiseSVN client. When
requesting for locks, I get this error message:

        Error: Lock request failed: 400 Bad Request (https://localhost)

Executing the svn client directly from the command line yields the same
result (svn lock -m "message" path/to/file.ext)

Checking Apache's logs leads me to this very weird error:

        [Mon Apr 30 18:03:08 2007] [error] [client] Tried to
attach multiple locks to a resource. [400, #405]

I've tried using svnserve and using the file:/// protocol directly, and
locking/unlocking is fine. I've Googled this topic and I only get vague
answers (someone suggested downgrading to Apache 2.0, my binaries are for
2.2, and downgrading to Subversion 1.4.2). The mailing list search didn't
give me useful results.

Does anyone have a solution to this?

Thanks in advance,

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 5 14:39:02 2007

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.