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

Re: Limiting the scope of an untagged If Header production (was: RE: If Header: evaluation of all assertions)

From: Stefan Eissing <stefan.eissing@greenbytes.de>
Date: Mon, 14 Oct 2002 10:43:46 +0200
Cc: "'Webdav WG'" <w3c-dist-auth@w3c.org>
To: "Clemm, Geoff" <gclemm@rational.com>
Message-Id: <0D66F312-DF51-11D6-9950-00039384827E@greenbytes.de>

Another possible "breakage" is use of the untagged if header for
PUT on unmapped resources. At least our server uses then the
untagged production to check the parent resource.

//Stefan

Am Sonntag, 13.10.02, um 19:36 Uhr (Europe/Berlin) schrieb Clemm, Geoff:

> I am somewhat concerned about the effect of this change on
> the semantics of existing clients.
>
> For example, do any clients today submit the etag of both the source
> and the destination resource of a MOVE in an untagged If production?
> If so, this change would remove the etag check on the Destination,
> and thereby break the overwrite protection for that request.
>
> But if we won't be breaking existing clients, I fully support this
> change, since it simplifies and clarifies the semantics of the
> If header.
>
> Cheers,
> Geoff 
>
> -----Original Message-----
> From: Lisa Dusseault [mailto:lisa@xythos.com]
>
> Also, I would clarify what the untagged if production refers to, and it
> should probably refer only to the resource named in the Request-URI.
>
Received on Monday, 14 October 2002 04:43:58 GMT

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