W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2006

Re: ETags vs Variants, was: Revising RFC2616 - what's happening

From: Henrik Nordstrom <hno@squid-cache.org>
Date: Mon, 06 Nov 2006 10:43:57 +0100
To: "Roy T. Fielding" <fielding@gbiv.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <1162806237.3612.15.camel@henriknordstrom.net>
sön 2006-11-05 klockan 17:34 -0800 skrev Roy T. Fielding:

> There is no issue here.  Vary works in many implementations and there
> has never been a single report of interoperability problems between
> clients and servers that have implemented Vary as specified.  It is an
> integral part of HTTP/1.x caching that cannot be deprecated.

While I agree with you in principle I am still a bit curious. Can you
name an implementation where Vary really works?

MSIE -> no-store

Firefox -> Stores at most one variant per URL. Broken if no ETag in the
response. In such case it's processed as kind of a no-cache and Sends
If-Modified-Since based on the old response, and the real error being
taking a 304 response to mean that the old response is valid for the new
request headers as well. ETag + If-None-Match prevents the bug from
surfacing if supported by the server.

Squid -> kind of attempts to obey Vary, but with limitations

Delegate -> no-store

Regards
Henrik

Received on Monday, 6 November 2006 15:30:38 GMT

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