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

Re: Method not allowed exception

From: Ben Reser <ben_at_reser.org>
Date: Sun, 17 Nov 2013 20:23:17 -0800

On 11/17/13 2:12 PM, Geoff Field wrote:
> Sorry for top-posting, but although Brane is right, he's not being as helpful as he could.
> Stefano, I had pretty much the same issue. A workaround is to only do actions (other than Commit) on unlocked working copies. That is, before doing a copy (in particular), make sure all locks are released.
> The fix that worked for me was to update the server. I downloaded the Wandisco server binaries (which are patched with the fix to this issue) and then copied mod_dav*.so to the modules directory of the Apache installation that we have actually working. (Ideally, I'd just install and run the Wandisco binaries, but with our configuration it was easiest to get working by just doing the copy.)

Your issue and the one he is having aren't similar at all.

He was trying to do a checkout against a URL that isn't directed at Subversion.
 Subversion uses HTTP methods that normally aren't typically used by a web
browser. As a result Apache HTTPD rejected the request by the Subversion
client with a Method Not Allowed (405) error rather than a Not Found (404)
error as he was expecting. This is normal behavior of Apache httpd (though
perhaps we could improve our error message to help a user realize this probably
means they're using the wrong URL or the server is misconfigured).

The problem you're describing is this bug with mod_dav:

Which happens when you try to commit a copy of a file that is locked and ended
up getting a Failed Dependency (424) error. That issue will be fixed in 2.2.26
and 2.4.7 when they come out.
Received on 2013-11-18 05:24:42 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.