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

RE: Comments regarding locking & auto-checkin...

From: Clemm, Geoff <gclemm@rational.com>
Date: Wed, 15 Aug 2001 17:45:51 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B103F8AB4A@SUS-MA1IT01>
To: "WebDAV (E-mail)" <w3c-dist-auth@w3.org>
   John asks:
   Is a PUT supposed to be rejected if the IF header provided specifies an
   invalid lock token and the resource is not locked?

   Jim Amsden replies:
   The if header would likely be ignored since the resource isn't
   locked and there's no token to check. But servers could implement
   this as a failed If header since it doesn't match the
   resource. Looks like a clarification might be needed in the spec.

I believe 2518 is reasonably clear on this point.  Section 9.4:

 The If header's purpose is to describe a series of state lists.  If
 the state of the resource to which the header is applied does not
 match any of the specified state lists then the request MUST fail
 with a 412 (Precondition Failed).  

So if you include a lock token, and it does not match the resource
to which you are applying the method, the PUT must fail with a 412.

Now there is some ambiguity about the meaning of "the resource
to which the header is applied" and no-tag-list productions.
For example, is the collection one of the resources to which
the header is applied, when you delete a member of the collection?
But that's a different discussion (:-).

Cheers,
Geoff
Received on Wednesday, 15 August 2001 17:37:18 GMT

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