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

Unable to use SVNMasterURI , getting (405 Method Not Allowed) in response to PROPPATCH request

From: Tal Abramson <tala_at_alphacsp.com>
Date: Mon, 25 May 2009 17:21:18 +0300

Hi all
i hope someone has encounter this behavior
All my searches came out with no answer for this problem

The situation is like so :
we have a customer in a different continent , and we wish to have a
mirror(slave) repository locally there
So we have the master in here (executing the sync on a hook), and the slave
other there (with SVNMasterURI to https)
But any time we try to commit to the slave repository we are getting:
svn ci -m"xx"
svn: Commit failed (details follow):
svn: At least one property change failed; repository is unchanged
svn: Server sent unexpected return value (405 Method Not Allowed) in
response to PROPPATCH request for
'/svn-master/!svn/wbl/73fb5655-9f3a-4ef9-b054-5db4e38fd86b/22'

I set up a different slave environment with the exact same settings , and it
worked perfect
When i looked at each server ssl_request_log , i see that the remote slave
has:
[25/May/2009:22:21:33 +0800] xx.xx.xx.xx TLSv1 DHE-RSA-AES128-SHA "PROPPATCH
/svn-master/!svn/wbl/dda6c9ab-dd18-4520-ab9c-476a8200feb4/24 HTTP/1.1" 976
"-" "SVN/1.5.4 (r33841) neon/0.28.2"

While the local slave does not have it
What is the sourse of this request?
How do i investigate this ?

we tried committing directly to the master from the remote network with
success
The syncs works fine
there are no authentications currently (as we are still in test phase)

Thanks in advanced
Best Regards
Tal

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2353491

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-25 16:23:49 CEST

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.