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

Re: HTTP/2 Upgrade with content?

From: Stefan Eissing <stefan.eissing@greenbytes.de>
Date: Sat, 14 Mar 2015 09:07:20 +0100
Cc: Daniel Stenberg <daniel@haxx.se>, "Jason T. Greene" <jason.greene@redhat.com>, Mike Bishop <Michael.Bishop@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <BB0E98C7-2D88-42B7-AF89-AE320057E907@greenbytes.de>
To: Greg Wilkins <gregw@intalio.com>
Greg,

totally agree. That is what mod_h2 is already doing and it will stay that way. It does also upgrade on any suitable request, not only the first. 



> Am 13.03.2015 um 23:21 schrieb Greg Wilkins <gregw@intalio.com>:
> 
> 
>> On 14 March 2015 at 01:21, Stefan Eissing <stefan.eissing@greenbytes.de> wrote:
>> - maybe a mixed 1.1 up and h2c down request could be made to work, but there seems no gain for anyone in creating this mythical beast.
> 
> Stefan,
> 
> it would not be impossible to implement this - except I see there is no way around the risk of deadlock if up is streamed or the DoS issue if up is held in memory.
> 
> So rather than encourage a false belief that such a mechanism might work for arbitrary content, I think it is better for servers to ignore all upgrades with any content.
> 
> cheers
> 
> 
> 
> 
> -- 
> Greg Wilkins <gregw@intalio.com>  @  Webtide - an Intalio subsidiary
> http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that scales
> http://www.webtide.com  advice and support for jetty and cometd.

Received on Saturday, 14 March 2015 08:07:46 UTC

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