Hi Rolf, to act on a locked resource it is necessary to give the lock token in the request. If I remember correctly, the spec recommends a client to send the lock token only if this client issued the lock. This way no client can steal the lock of another client of the same user. If you want to act on the resource with another client, read the lock token and send it with the request. So it should be possible the steal the lock of the other session.
Regards, Andreas On 9 Apr 2004 at 9:56, Rolf Kulemann wrote: > Is it "normal" behaviour, that I can not i.e. update a locked resource > as the same user, which locked the resource, if I try to update the > resource in a different session in which the lock was created? > > To reproduce it (Using a webdav client): > > - login as user A -> session x > - "lock files/norace.xml" > - login again as user A -> session y > - session y: put src.xml norace.xml -> Status 423 (locked?) > > I ask only to make sure if this is "a defined WebDAV behaviour". Reading > the WebDAV spec. I could not find the answer. Or is this behaviour slide > specific? > > > -- > Regards, > > Rolf Kulemann > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
