W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

Re: [#153] PUSH_PROMISE headers

From: James M Snell <jasnell@gmail.com>
Date: Sat, 29 Jun 2013 07:27:04 -0700
Message-ID: <CABP7Rbe==JGEr9ro9hUoW7HQCA6a+acryzic1HswftbSgvFy9Q@mail.gmail.com>
To: Amos Jeffries <squid3@treenet.co.nz>
Cc: ietf-http-wg@w3.org
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

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:13 UTC