W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2010

Re: Issue 39: proposed example for varying the etag based on conneg

From: Henrik Nordström <henrik@henriknordstrom.net>
Date: Tue, 04 May 2010 01:31:52 +0200
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Jamie Lokier <jamie@shareable.org>, Yves Lafon <ylafon@w3.org>, nathan@webr3.org, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <1272929512.24081.71.camel@localhost.localdomain>
tis 2010-04-06 klockan 17:37 +0200 skrev Julian Reschke:

> > A weak entity tag SHOULD change whenever the origin server considers prior representations to be unacceptable as a substitute for the current representation. In other words, an entity tag SHOULD change whenever the origin server wants caches to invalidate old responses.

True, and gets more obvious if you look at what happens when content
negotiation is used on the resource.

Any responses with matching ETag must be fully interchangeable with
another having the same ETag. No matter if weak or strong.

Two responses which are not fully interchangeable MUST NOT use the same
ETag.

Responses which are fully interchangeable but which perhaps do not share
the same binary representation MAY use a shared weak ETag.

Regards
Henrik
Received on Monday, 3 May 2010 23:32:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:18 GMT