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

The Big Lie : if (info->r->method_number == M_LOCK) BUG?

From: Pauli Ojanperä <pauli.s.t.vaahterametsa_at_jyu.fi>
Date: Mon, 5 Oct 2009 18:19:36 +0300 (EEST)

Hello!

I was investigating a Subversion locking bug reported here:
http://svn.haxx.se/users/archive-2009-07/0169.shtml

My own experience of the bug tells that any tries of a MS Office application
to refresh its lock do fail. By running "svnadmin lslocks repo" we can
confirm that the initial locking succeeds. However, mod_dav is not getting
the information of the lock token's existence, and fails on the "If:"
precondition manifested in the lock refresh request header.

Apache logs say:
Could not LOCK /repo/nnn.txt due to a failed precondition (e.g. other
locks). [412, #0]
The precondition(s) specified by the "If:" header did not match this
resource. At least one failure is because: a State-token was supplied, but
it was not found in the locks on this resource. [412, #0]

It seems to me that the commit linked below causes mod_dav_svn to be
unable to confirm the precondition (the existence of a locktoken) to
continue fulfilling a lock refresh request.

http://svn.collab.net/viewvc/svn/trunk/subversion/mod_dav_svn/lock.c?r1=19508&r2=19509&

What do you think?

Pauli

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2403724
Received on 2009-10-05 18:04:50 CEST

This is an archived mail posted to the Subversion Dev mailing list.