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

PUT question

From: Keith Wannamaker <krw@raleigh.ibm.com>
Date: Wed, 04 Aug 1999 12:14:12 -0400
Message-ID: <37A866D4.9689D0A9@raleigh.ibm.com>
To: w3c-dist-auth@w3.org
The question, up front, is should a PUT request to a lock-null resource
also validate the lock-null resource's parent collection against the If
header?

The background to the question-
The PUT request involves writing to the uri's parent collection, so, in
mod_dav, it always validates both the uri and the uri's parent for null
resources.  

Thus, if /foo is a locked or lock-null resource, while / is not locked,
should the following request fail?

PUT /foo HTTP/1.1
If: (<opaquelocktoken:......>)
.

The If header doesn't specify any uri's, so both /foo and / are
validated against the lock token.  If /foo is a lock-null resource, and
/ has not been locked, I assume this request generates a 412
Precondition failed.

A successfully request specifies a uri-

PUT /foo HTTP/1.1
If: </foo> (<opaquelocktoken:......>)
.

This seems consistent with the spec, but a little unintuitive.  I don't
know of any locknull-aware mainstream clients, so I suppose this is new
ground.  Is this indeed the spirit of 2518?

Thanks for any input,
Keith 
--
Keith Wannamaker
IBM HTTP Server Development
RTP NC, USA
Received on Wednesday, 4 August 1999 12:14:55 GMT

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