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

RE: Lock request failed: 405 Method Not Allowed

From: Evan Stark <EStark_at_point-inc.com>
Date: 2005-09-29 07:36:08 CEST

Hi Bob,

We were getting this for a while with some users but not others. Turned out
to be a typo in the access control file.

- jevans

-----Original Message-----
From: bob@proulx.com - Wednesday, 28 September 2005 7:18 pm

I have upgraded to svn 1.2.0 (I realize this is slightly old but a
package was conveniently available and I don't think this difference
is affecting me). Locking works when using the svn+ssh:// or file://
transports. But locking fails for me when using https://. The
message I see is the following, with my url munged.

  svn lock foo
  svn: Lock request failed: 405 Method Not Allowed (https://example.com)

Because I know that locking works using two of the three methods I
know that svn itself is okay for locking. Or at least I believe so.
But I must be missing a component upgrade in the https:// path that is
needed to support this. But I don't know what. Or perhaps when this
svn was built the autodetection somewhere along the way did not
configure this in. I am stuck. Any hints?


This email message is certified Virus Free.  Scanned by FrontBridge Technologies, Inc.  http://www.frontbridge.com
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 29 07:37:33 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.