W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2015

Re: HTTP/2 Upgrade with content?

From: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Date: Fri, 13 Mar 2015 11:42:42 +0200
To: "Jason T. Greene" <jason.greene@redhat.com>
Cc: Greg Wilkins <gregw@intalio.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20150313094242.GA16018@LK-Perkele-VII>
On Fri, Mar 13, 2015 at 04:28:46AM -0400, Jason T. Greene wrote:
> What about draining the content and after the 101 the h2 response
> sends a 307?

Might work if you never send a 100 (including implicitly by waiting
too long). 100-Continue may mean that the data transfer can't
be retried after it starts.

And if the client app is has simplistic redirect checking (just
count redirects), one could even 307 to self...


I.e, as flow:
- POST to foo (with upgrade to h2c and 100-expect)
- 101 to h2c
- 307 to foo
- POST to foo (with 100-expect)
- 100
- <payload>
- 200


-Ilari
Received on Friday, 13 March 2015 09:43:08 UTC

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