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

HTTP If-* headers

From: Stefan Eissing <stefan.eissing@greenbytes.de>
Date: Fri, 26 Apr 2002 18:19:28 +0200
To: w3c-dist-auth@w3c.org
Message-Id: <62272144-5931-11D6-9959-00039384827E@greenbytes.de>
You saw this coming, didn't you? ;)

The HTTP If-* header family, namely

If-Match, If-None-Match, If-Modified-Since,
If-Unmodified-Since and If-Range

are described in rfc2616 as they apply to

But what about the WebDAV methods? I think we need
to clarify and put an advisory in an updated rfc2518.

Easy things first: If-Range seems only to make sense
with GET. So we could exclude it from discussions of
other methods.

The other four, IMO, should be honoured on DELETE,

But what about PROPFIND? For the If-* headers to make
sense with PROPFIND, a client would rely on the
assumption that DAV:getlastmodified and DAV:getetag
change when properties are changed (either by PROPPATCH
or as a side-effect on live properties from other

Would the burden on the server (to update etag/lastmodified)
justify the benefit? I rather doubt that, but would like
to hear the opinion of the excellent audience on this list.

Received on Friday, 26 April 2002 12:20:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:25 UTC