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

Re: :scheme and CONNECT method

From: (wrong string) 陈智昌 <willchan@chromium.org>
Date: Tue, 13 Aug 2013 23:31:46 +0200
Message-ID: <CAA4WUYgGvzK=+46KxABybzyCJ1BsTAezrYjL2fncTc1gpyeBMA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: James M Snell <jasnell@gmail.com>, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
James, can you explain why you prefer deprecating CONNECT? It's a fairly
widely used HTTP feature. Browsers tunnel SSL to the origin server over
HTTP proxies using CONNECT. It seems rather bad to remove this capability.
Or do you mean you just think we should file an issue (already done) and
address it later?

Note that Chromium indeed already supports this functionality and it's been
in use in production for awhile now, at least by Googlers using Chrome.


On Tue, Aug 13, 2013 at 11:20 PM, Martin Thomson
<martin.thomson@gmail.com>wrote:

> On 13 August 2013 22:14, James M Snell <jasnell@gmail.com> wrote:
> > While I'm certainly not going to spend any time arguing this one much,
> > my vote is to deprecate CONNECT in HTTP/2 with the recognition that
> > doing so removes a feature that currently exists in HTTP/1. Later, a
> > better approach for handling the use case can be determined.
>
> That's certainly a valid answer.  But we have folks here with some
> experience with CONNECT in SPDY.  Maybe their experience will provide
> enlightenment.
>
Received on Tuesday, 13 August 2013 21:32:13 UTC

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