Re: HTTP 2.0 "Upgrade" flow

Do we know how effective that is? I've no idea how often transparent
proxies bother about correctness w.r.t. things like this :(
-=R


On Tue, Apr 16, 2013 at 10:54 PM, Amos Jeffries <squid3@treenet.co.nz>wrote:

> 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
>
>
>