Re: HTTP 2.0 "Upgrade" flow

• From: Amos Jeffries <squid3@treenet.co.nz>
• Date: Wed, 17 Apr 2013 17:54:46 +1200
• To: ietf-http-wg@w3.org
• Message-ID: <516E3926.7010402@treenet.co.nz>

On 17/04/2013 5:18 p.m., Roberto Peon wrote:
> As proposed by Gabriel, SETTINGS (or equivalent) would/could be 
> carried in the headers in the UPGRADE request.
> However, this isn't enough by itself-- you still want to cause 
> transparent proxies to barf when you start speaking HTTP/2 if they're 
> not going to be able to handle it.

This is why the original proposal by Willy T. listed each of the HTTP/2 
"seeding" headers sent over HTTP/1.1 in the Upgrade request as a 
Connection header alongside Connection:Upgrade. So intermediaries would 
strip them away as well and break the Upgrade attempt cleanly.

Amos

Received on Wednesday, 17 April 2013 05:55:17 UTC