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

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

From: Felipe Gasper <felipe@felipegasper.com>
Date: Thu, 21 Dec 2017 17:51:43 -0500
Message-Id: <95A42BD0-03CD-445A-B833-3D3351765AC7@felipegasper.com>
To: ietf-http-wg@w3.org

	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 Thursday, 21 December 2017 22:52:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:11 UTC