- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Fri, 28 Jun 2013 17:21:04 -0700
- To: HTTP Working Group <ietf-http-wg@w3.org>
https://github.com/http2/http2-spec/issues/153 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 response).
Received on Saturday, 29 June 2013 00:21:32 UTC