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

Re: HTTP2: ETag, If-None-Match, and RST_STREAM

From: Matthew Kerwin <matthew@kerwin.net.au>
Date: Fri, 22 Dec 2017 10:58:02 +1000
Message-ID: <CACweHNAbhyffBQMVc4_w7Sdt5YZHqDKWF1xbGe4Z7cnPjzUGxQ@mail.gmail.com>
To: Felipe Gasper <felipe@felipegasper.com>
Cc: ietf-http-wg@w3.org
On 22 December 2017 at 08:51, Felipe Gasper <felipe@felipegasper.com> wrote:
> Hello,
>         Does HTTP/2 expect that a browser that:
> 1) Receives a PUSH_PROMISE with if-none-match = "hahaha"
> 2) Has that resource cached but with etag = "qweqwe"
> … will accept the new copy of the resource rather than sending RST_STREAM and using its cache?
>         I’ve been testing this and can’t seem to get it to work this way. It keeps using the cache every time, even when I send a new etag. I’ve dug around several articles today on HTTP/2 caching, and I can’t find this level of detail in any of them. I’m not sure if my server setup is at fault, if the browsers are at fault, or if this just isn’t how it’s meant to work.
>         Thank you!
> -Felipe Gasper
> Mississauga, Ontario

Hi Felipe,

Does the pushed response include the etag:"hahaha" header field, and
all the other cache-control stuff?  I would imagine that that's more
important to the browser than whatever was in the virtual request
(although I'm not a browser person, so I can't say for sure.)

  Matthew Kerwin
Received on Friday, 22 December 2017 00:58:26 UTC

This archive was generated by hypermail 2.3.1 : Friday, 22 December 2017 00:58:33 UTC