8.1 Lock Tokens

Every lock is identified with a token that must be universally unique. The lock token must be used in subsequent requests to change the locked resource or to unlock it.

Each lock token is a URI. Most servers use the opaquelocktoken: URI scheme defined by WebDAV for this purpose. The opaquelocktoken: scheme is used to construct valid URIs containing only a UUID followed by optional custom characters.

 opaquelocktoken:f81d4fae-7dec-11d0-00a0c91e6bf6#myserver1234 

It is also legal to use any syntactically correct URI, including a URL. For example:

http://example.com/locktokenURLspace/1234-5678-9012.lock

Since the lock token is opaque to the client, the uniqueness and the server's performance concerns (in generating lock tokens or looking up locks) are more important than how it looks or what kind of URI it is.

Clients must store the lock token in order to use it later to modify the resource or to refresh or remove the lock.