truefor your provider:
UNLOCK, as described below.
UNLOCKare seen as an extension of the CRUD operations, so are issued to
LOCKfor that document.
Timeout: Second-600header (here for a 10 min lock), per RFC 2518 section 9.8.
<d:lockinfo>XML document, which looks as follows. The
<d:locktype>are for compliance with RFC 2518, but for now only the values below are supported.
<d:lockinfo>document with information about the owner of the lease (same document that was provided when the lease was acquired), and a
Timeoutheader telling the caller for how much longer the lease is expected to stay in place. This timeout value is only indicative as after your response the lease can be canceled by the user (see
UNLOCKbelow) or renewed (by issuing another
UNLOCKmethod with a
<d:lockinfo>document in the request body. Based on the information in this document, if following the same logic used for the
LOCKmethod, the lease:
Timeoutheader, and a
<d:lockinfo>document in the response body, similarly to what is done for the LOCK method.