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

HTTP/2 extensions and proxies

From: Gábor Molnár <gabor.molnar@sch.bme.hu>
Date: Mon, 30 Sep 2013 08:54:07 +0200
To: HTTP Working Group <ietf-http-wg@w3.org>
Message-id: <CA+KJw_6sMky9hPqbi4F2T7BiVuzrEU_y4_nWkh0=3sFHajEQZw@mail.gmail.com>
Currently, "Implementations MUST ignore frames of unsupported or
unrecognized types.". As far as I see, the point of this is to enable
the extension of the protocol in a backwards compatible way.

But what about proxies? Should they ignore unrecognized frames too, or
should they forward them? If they drop every unknown frame, it is not
possible to specify end-to-end extensions. Is this constraint
intentional? I think that end-to-end extensions would be useful, too,
e.g. WebSockets over HTTP2 if a HTTP2 proxy does not support
WebSockets explicitly.

Received on Monday, 30 September 2013 06:54:57 UTC

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