W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2006


From: <bugzilla@soe.ucsc.edu>
Date: Sat, 14 Jan 2006 10:48:39 -0800
Message-Id: <200601141848.k0EImdgC023765@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org


julian.reschke@greenbytes.de changed:

           What    |Removed                     |Added
            Version|-07                         |-10

------- Additional Comments From julian.reschke@greenbytes.de  2006-01-14 10:48 -------
Proposed text (see also

Section 7., para. 72:

 7.7.1  Example - Write Lock


 7.7.1  Example - Write Lock and COPY

Section 7., para. 78:

 7.8  Write Locks and COPY/MOVE


 7.7.2  Example - Deleting a member of a locked collection
    Consider a collection /locked exclusively write-locked with Depth:
    Infinity, and an attempt to delete an internal member /locked/member:
      DELETE /locked/member HTTP/1.1
      Host: example.com
    This request would fail because the lock token for the collection
    lock was not submitted with the request:
      HTTP/1.1 423 Locked
      Content-Type: application/xml; charset="utf-8"
      Content-Length: xxxx
      <?xml version="1.0" encoding="utf-8" ?>
      <D:error xmlns:D="DAV:">
    Thus the client would need to submit the lock token with the request
    to make it succeed.  To do that, various forms of the If header (see
    Section 9.4) could be used:
    "No-Tag-List" format (see Section 9.4.1)
    If: (<urn:uuid:150852e2-3847-42d5-8cbe-0f4f296f26cf>)
    "Tagged-List" format, for http://example.com/locked/ (see
    Section 9.4.2)
    If: <http://example.com/locked/>
    "Tagged-List" format, for http://example.com/locked/member (see
    Section 9.4.2)
    If: <http://example.com/locked/member>
    Note that for the purpose of submitting the lock token the actual
    form doesn't matter; what's relevant is that the lock token appears
    in the If header, and that the If header itself evaluates to true.
 7.8  Write Locks and COPY/MOVE

------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Saturday, 14 January 2006 18:48:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:35 UTC