- From: Geoffrey M. Clemm <geoffrey.clemm@rational.com>
- Date: Tue, 25 Jan 2000 13:10:24 -0500
- To: w3c-dist-auth@w3.org
From: jamsden@us.ibm.com If the lock token isn't returned in the header, there's no way for you to get the lock token of the lock you just created. Section 6.3 of RFC-2518 states that you can get the lock token through the lock discovery property: "A lock token is a type of state token, represented as a URI, which identifies a particular lock. A lock token ... can also be found through lock discovery on a resource." That's because the active lock element of the lock discovery property does not contain the authentication id of the principal owning the lock. I can find no authentication id defined or required by RFC-2518. In fact, RFC-2518 explicitly states that an authentication id is not part of the WebDAV protocol: "Locks MUST be enforced based upon whatever authentication mechanism is used by the server, not based on the secrecy of the token values." and: "User agent authentication has previously occurred via a mechanism outside the scope of the HTTP protocol, in an underlying transport layer." The lock tokens are in the lock discovery, but you can't figure out which ones you own. This information is provided by the DAV:owner element in the lockdiscovery property. I continue to believe this is an open issue that requires clients to persist their lock tokens outside the WebDAV repository. Lock tokens are a pain enough for the rare case where they are actually useful. How else do you handle the situation where the same principal has several clients acting against the same resource? I believe this will be a common scenario. Cheers, Geoff
Received on Tuesday, 25 January 2000 13:10:30 UTC