W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2001

Re: Inconsistency in lock-token response requirements in 2518

From: Jason Crawford <ccjason@us.ibm.com>
Date: Tue, 18 Sep 2001 18:55:15 -0400
To: "Jason Crawford" <ccjason@us.ibm.com>
Cc: Daniel Brotsky <dbrotsky@adobe.com>, "Webdav WG" <w3c-dist-auth@w3c.org>, w3c-dist-auth-request@w3.org
Message-ID: <OF108A6F83.5417EA95-ON85256ACB.007DC711@pok.ibm.com>

I've updated the issues list to reflect the fact that we need to make some
obvious editing changes to the examples.

Phone: 914-784-7569,   ccjason@us.ibm.com

                    Crawford/Watson/IB       To:     Daniel Brotsky <dbrotsky@adobe.com>                     
                    M@IBMUS                  cc:     "Webdav WG" <w3c-dist-auth@w3c.org>                     
                    Sent by:                 Subject:     Re: Inconsistency in lock-token response           
                    w3c-dist-auth-requ        requirements in 2518                                           
                    09/12/2001 05:06                                                                         

This issue is in the issues list....


Section 8.10.1 explicitly states that the response from a successful lock
request MUST include the Lock-Token header, yet the examples in 8.10.8,
8.10.9, and 8.10.10 aren't compliant with this requirement, and should be

And my recollection is the same as yours.  I think we established, in a
discussion lead by Jim Amsden a few years ago, that the header must be
included in the header for just the reason you stated.   Unless someone
speaks up in the next few days, I'll mark that as resolved as an obvious
editing correction to the spec.


Phone: 914-784-7569,   ccjason@us.ibm.com
Received on Tuesday, 18 September 2001 22:08:02 UTC

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