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

Re: END_STREAM flag and trailing headers

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sat, 10 May 2014 09:36:09 +0200
Message-ID: <536DD6E9.9040508@gmx.de>
To: David Krauss <potswa@gmail.com>
CC: Martin Thomson <martin.thomson@gmail.com>, Greg Wilkins <gregw@intalio.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 2014-05-10 05:08, David Krauss wrote:
> On 2014–05–09, at 2:16 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
>> The question about a safe method that allows a request body comes up over and over, and right now people use POST for it. If we ever define that method, it won't be supported in HTTP2 push.
> Can you clarify? Pushes eliminate (or “skip over”) the request by definition. Pushing a redirect or error simply anticipates a client request with such a response. POST (or anything with a request body) would usually bypass prior PUSH_PROMISEs along with the rest of the cache. An exception to this rule could be defined in HTTP/2 using multiple header blocks, and perhaps segmentation: push the request, then the response. But, it would have to be an application-specific extension for now.

I'm not sure *what* needs to be clarified. Can you clarify?

The use case is pushing responses for safe requests that *do* have q 
request body, such as a directory update (PROPFIND).

Best regards, Julian
Received on Saturday, 10 May 2014 07:36:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:30 UTC