W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2012

Re: #385: HTTP2 Upgrade / Negotiation

From: Yoav Nir <ynir@checkpoint.com>
Date: Thu, 25 Oct 2012 15:21:46 +0200
To: Patrick McManus <pmcmanus@mozilla.com>
CC: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, Mark Nottingham <mnot@mnot.net>, Willy Tarreau <w@1wt.eu>, Amos Jeffries <squid3@treenet.co.nz>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <874F094A-2EEE-4574-827A-6677143748A2@checkpoint.com>

On Oct 25, 2012, at 3:01 PM, Patrick McManus wrote:

> I know this has been said before by the Chrome team, but I too am starting to see websocket bugs pile up due to transparent proxies that don't speak upgrade and explicit proxies that don't let you tunnel to port 80 as configured.

Transparent proxies should learn about Upgrade: and either support websockets/http2 or remove the header. Hopefully they will have done this by the time HTTP/2.0 over port 80 is actually deployed.

> (bluecoat and MS ISA/TMG are the most common I hear about). ws:// hasn't been very successful in those environments but wss:// has been. Good thing that in the websockets world there aren't a lot of legacy urls to worry about - not true for http :(
> 
> For http2, I don't think it is enough to just fail fast to http/1 when for most cases we could get those users speaking HTTP/2 over tls on 443. A mechanism like Alternate-Protocol accomplishes that and I think that is a more important property than upgrading in band (which is admittedly nice!).

So rather than go to HTTP/1.1 you'd prefer going to TLS with an anonymous ciphersuite?  I don't think that would help much, as the transparent proxies that also MitM SSL are getting ever more popular.

> As for caching successful upgrades or successful A-P's they pretty much have the same set of tradeoffs.

Yes, but I don't think it's all that bad. Browsers and operating systems have some feeling of location, which changes when any of your IP addresses change, or your routing table changes, or the configuration of the proxy or DNS servers changes. Browsers notice these things so that they can quickly re-establish connections, re-query the DNS, and reload pages that had some failure.  If you have this event also invalidate the cache, so that you go through the Upgrade handshake again, you should usually not have a case where a proxy has suddenly got in your path and won't let you use HTTP/2 over TCP port 80 any more.

Yoav
Received on Thursday, 25 October 2012 13:23:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 25 October 2012 13:23:34 GMT