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

Re: Submitted new I-D: Cache Digests for HTTP/2

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 15 Jan 2016 17:33:15 +1100
Message-ID: <CABkgnnUrbBzKRZZsRzAf93A1Gj3AZQAfNpnBQLRqXzQFnRNwwA@mail.gmail.com>
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: Ilya Grigorik <ilya@igvita.com>, Stefan Eissing <stefan.eissing@greenbytes.de>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
On 15 January 2016 at 17:23, Kazuho Oku <kazuhooku@gmail.com> wrote:
> A server should merge the values of the cache-digest headers to
> construct the client's cache digest.


I don't think that this would be a good idea.  I would rather try to
use the "scope" parameter to narrow things down, to omit the header
field if there aren't changes, or rely on the server performing some
sort of "magic" tracking based on what it has sent.

The upshot of using a header field is that this really means that this
isn't hop-by-hop information.  Like Ilya said, I doubt that's a huge
problem.  Nothing stopping an intermediary from consuming, modifying,
or inserting the value though.
Received on Friday, 15 January 2016 06:33:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 March 2016 12:47:10 UTC