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

Re: :scheme and CONNECT method

From: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Date: Wed, 14 Aug 2013 16:54:58 +0900
Message-ID: <CAPyZ6=+MU+G2ULH6AzA0hssEWqyXqmM92KtwYjsF74f=cti3tQ@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: William Chan (陈智昌) <willchan@chromium.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On Wed, Aug 14, 2013 at 2:35 AM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 13 August 2013 15:42, William Chan (陈智昌) <willchan@chromium.org> wrote:
> > I suggest opening an issue for this.
>
> https://github.com/http2/http2-spec/issues/230
>
> Just spit-balling, but I think that the '*' form is a better way to
> deal with this, i.e.,
>
> :method = CONNECT
> :scheme https
> :host example.org:443
> :path *
>
>
I'm fine with these values as long as it is clearly defined in the spec..
but proxy may not use the value of scheme in this case because
the tunneled protocol may be unknown to the proxy.


> The trick here is that the DATA frames that form the "request body"
> constitute a separate channel that is reliable, in-ordered, etc...
> This channel can be used to perform a TLS handshake and run any
> protocol you like.
>

This is what the SPDY proxy currently does as far as I know.

Best regards,

Tatsuhiro Tsujikawa
Received on Wednesday, 14 August 2013 07:55:45 UTC

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