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

Re: dont-revalidate Cache-Control header

From: Mark Nottingham <mnot@mnot.net>
Date: Thu, 16 Jul 2015 11:26:42 +0200
Cc: Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <54973543-2406-4188-8DCD-AE3C85ACB76A@mnot.net>
To: Ben Maurer <ben.maurer@gmail.com>

> On 14 Jul 2015, at 2:36 pm, Ben Maurer <ben.maurer@gmail.com> wrote:
> Static is a fairly reasonable name. Static does imply that the resource will *never* be revalidated (ever) vs the dont-reload which implies no revalidations prior to expiration. I don't have any preferences between the two but wanted to call that out.
> What's the next step here? 

Writing a small spec. Is there anyone who has experience doing this that's interested in helping out here? E.g., Ilya?


Mark Nottingham   https://www.mnot.net/
Received on Thursday, 16 July 2015 09:27:10 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:50 UTC