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

[Bug 129] LOCK_BODY_SHOULD_BE_MUST

From: <bugzilla@soe.ucsc.edu>
Date: Fri, 9 Dec 2005 21:37:51 -0800
Message-Id: <200512100537.jBA5bp3R007818@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=129

ejw@cs.ucsc.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From ejw@cs.ucsc.edu  2005-12-09 21:37 -------
I reviewed the -08 specification. Section 8.11 states:

   Lock method requests to create a new lock MUST have a XML
   request body which contains an owner XML element and other
   information for this lock request.

Section 8.11.1 states:

   A lock is refreshed by sending a LOCK request without a request body
   to the URL of a resource within the scope of the lock.

This addresses the issue by clarifying the difference in behavior between a new
lock creation and a lock refresh.

Closing the issue.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Saturday, 10 December 2005 05:38:25 GMT

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