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: Ilya Grigorik <ilya@igvita.com>
Date: Thu, 14 Jan 2016 06:13:01 -0800
Message-ID: <CAKRe7JGUUAinAqM9yHnUp0gJm5qwq5xvMhEo+fMnffRW7Kmu7w@mail.gmail.com>
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: Stefan Eissing <stefan.eissing@greenbytes.de>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
On Thu, Jan 14, 2016 at 12:55 AM, Kazuho Oku <kazuhooku@gmail.com> wrote:

> So a SW trying to send cache digest needs to send the value without
> designating it as a hop-by-hop header.  And that means that if a H2
> origin server sees the header, it needs to determine if the request
> came through an intermediary, and only use the value if it did not.
> Or else, a server might end up repeatedly pushing resources to a
> caching proxy that already has them cached.
> This looks like a hack to me, and I am not sure if it should be
> permitted within a specification, even though I believe it would work
> effectively (as we are doing in H2O).

With HTTPS in place, I think you can make some reasonable simplifying
assumptions here.. that'll make things work in practice.

Received on Thursday, 14 January 2016 14:14:12 UTC

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