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

Forcing validation

From: Mark Nottingham <mnot@mnot.net>
Date: Sat, 24 Jul 2010 17:15:32 +0200
Message-Id: <29B6F8E2-801B-4CF3-A807-CE24D1D634D8@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>
We currently have this text:

  If an origin server wishes to force a cache to validate every request, it can
  assign an explicit expiration time in the past. This means that the response is always
  stale, so that caches should validate it before using it for subsequent requests.

with the following note:

  This wording might cause confusion, because the response might still be served stale.

I.e., if you want to force validation, you should really use no-store or max-age=0, must-revalidate (as is said elsewhere).

This text originated in 2616. Any objection to just removing it?

Cheers,

--
Mark Nottingham     http://www.mnot.net/
Received on Saturday, 24 July 2010 15:16:01 GMT

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