- From: James M Snell <jasnell@gmail.com>
- Date: Sat, 29 Jun 2013 07:27:04 -0700
- To: Amos Jeffries <squid3@treenet.co.nz>
- Cc: ietf-http-wg@w3.org
Received on Saturday, 29 June 2013 14:27:30 UTC
On Jun 29, 2013 1:03 AM, "Amos Jeffries" <squid3@treenet.co.nz> wrote: > [ snip ] > > The above example is a good one. > > The cache will store the pushed response under: > hash(URL)+hash(Vary:"image/jpeg") > > When looking up future HIT the cache for this client on explicit-GET it will look up > hash(URL)+hash(Vary:"text/html, image/jpeg, image/gif") > > I assume you can spot the difference. > I didn't miss that. Pushed resources and content negotiation used together have rather, um, "interesting" complications. However, those don't change the request headers in the push promise and response headers in the HEADERS question which is what I was addressing. - James
Received on Saturday, 29 June 2013 14:27:30 UTC