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

Re: HTTP 1.1 --> 2.0 Upgrade

From: Nicolas Mailhot <nicolas.mailhot@laposte.net>
Date: Tue, 21 Aug 2012 15:25:03 +0000 (UTC)
To: ietf-http-wg@w3.org
Message-ID: <loom.20120821T172402-458@post.gmane.org>
Yoav Nir <ynir@...> writes:

> A related but orthogonal issue is finding out if the path between the client
> and the server supports HTTP/2.0. Fortunately, middleware does not tend to
> appear mid-path.

That depends what you call "mid-path". Middleware appears at network boundaries.
VPNs now enable easy stacking of multiple private networks, and the boundary the
middleware is deployed on can end up quite a long path away from the client.

> Client side middleware is either there or it's not. It's not likely to be
> present on-path to one generally available website while not being present
> for another.

If things were that simple no one would use PAC files. Their whole point is that
middleware is not a simple binary setting.
Received on Tuesday, 21 August 2012 15:25:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 21 August 2012 15:25:50 GMT