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

Re: ID for Immutable

From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
Date: Fri, 28 Oct 2016 17:44:05 +0300 (EEST)
To: Patrick McManus <pmcmanus@mozilla.com>, HTTP working group mailing list <ietf-http-wg@w3.org>
CC: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
Message-Id: <20161028144407.48EFF162D1@welho-filter4.welho.com>
> Htmlized:       https://tools.ietf.org/html/draft-mcmanus-immutable-00

|    o  User-Agents often provide two different refresh mechanisms: reload
|       and some form of force-reload.  The latter is used to rectify
|      interrupted loads and other corruption.  These reloads should
|      ignore immutable as well.

How about making it

Cache-Control: max-age=31536000, immutable=<hash-function-value>

So that immutable does not have effect if result of hash-function
does not give same value that what is value of immutable
cache control.

Several immutable cache controls are invalid if they are result
of same hash-function.

If server can't calculate hash-function over resource,
is is really static non-caching resource?

I think that this protects agaist that interrupted loads
becomes immutable.

/ Kari Hurtta
Received on Friday, 28 October 2016 14:44:42 UTC

This archive was generated by hypermail 2.3.1 : Friday, 28 October 2016 14:44:46 UTC