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

That is an interesting question and probably at the current stage very
implementation-specific (see e.g. [1])

You may also want to look at a previous discussion regarding this topic [2].

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=232040
[2] https://lists.w3.org/Archives/Public/ietf-http-wg/2016JulSep/0522.html

Why would a user agent cancel a pushed stream with hahaha?

Qapla'!
Benedikt

2017-12-21 23:51 GMT+01:00 Felipe Gasper <felipe@felipegasper.com>:
> 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

Received on Friday, 22 December 2017 00:53:17 UTC