W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2005

Re: [Bug 23] lock discovery vs shared locks

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sat, 29 Oct 2005 15:15:36 +0200
Message-ID: <436375F8.3060703@gmx.de>
To: Lisa Dusseault <lisa@osafoundation.org>
CC: w3c-dist-auth@w3.org

Clarifying one thing on second read:

Lisa Dusseault wrote:
>...
> There were some comments in a previous email from Julian about how the 
> lock token might not appear in the 'lockdiscovery' property if there are 
> multiple (shared) locks on the resource. This statement doesn't fit my 

No, what I said (or meant to say is) that looking at DAV:lockdiscovery 
in general will not help you at all, because it may contain *multiple* 
entries (Geoff correctly pointed out later that it may not be there at all).

The only *reliable* way to find out the lock token a LOCK request 
created is to look at the "Lock-Token" response header. This is the only 
method that will always work, so please let's not waste time confusing 
people by talking about other methods that may or may not work.

> understanding, so I haven't yet "fixed" that if I am indeed wrong. 
> Doesn't the 'lockdiscovery' property include every active lock on the 
> resource and all their lock tokens?

It includes whatever the server wants to reveal. Citing 
<http://greenbytes.de/tech/webdav/rfc2518.html#rfc.section.13.8>:

"The server is free to withhold any or all of this information if the 
requesting principal does not have sufficient access rights to see the 
requested data."

Best regards, Julian
Received on Saturday, 29 October 2005 13:16:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:11 GMT