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

[#153] PUSH_PROMISE headers

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 28 Jun 2013 17:21:04 -0700
Message-ID: <CABkgnnVGh9dLkfDrO2fq5TsnxwEu0Dff=LqJEJR5Odq2ibfDMg@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>

The current text describes PUSH_PROMISE as having a few request
headers, plus some response headers, but it's quite vague.

I think that if this is going to be properly workable across a wide
range of uses with lots of different headers, PUSH_PROMISE needs to
include two sets of headers: the ones that it overrides from the
associated request (:path being foremost of those) and the ones that
it provides as a "preview" of the response (e.g., ETag might allow
caches to determine if they were interested in the rest of the
Received on Saturday, 29 June 2013 00:21:32 UTC

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