Re: WebSocket2

Ilari Liusvaara <ilariliusvaara@welho.com> Sun, 02 October 2016 17:24 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B15FC12B0D9 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 2 Oct 2016 10:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.917
X-Spam-Level:
X-Spam-Status: No, score=-9.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JEFxe1Gm3sLo for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 2 Oct 2016 10:24:07 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 050AE12B0CA for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 2 Oct 2016 10:24:06 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bqkQU-000356-0H for ietf-http-wg-dist@listhub.w3.org; Sun, 02 Oct 2016 17:19:46 +0000
Resent-Date: Sun, 02 Oct 2016 17:19:46 +0000
Resent-Message-Id: <E1bqkQU-000356-0H@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <ilariliusvaara@welho.com>) id 1bqkQQ-00032B-FD for ietf-http-wg@listhub.w3.org; Sun, 02 Oct 2016 17:19:42 +0000
Received: from welho-filter2.welho.com ([83.102.41.24]) by maggie.w3.org with esmtp (Exim 4.80) (envelope-from <ilariliusvaara@welho.com>) id 1bqkQN-000141-Bc for ietf-http-wg@w3.org; Sun, 02 Oct 2016 17:19:41 +0000
Received: from localhost (localhost [127.0.0.1]) by welho-filter2.welho.com (Postfix) with ESMTP id 909E51327E; Sun, 2 Oct 2016 20:19:11 +0300 (EEST)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp2.welho.com ([IPv6:::ffff:83.102.41.85]) by localhost (welho-filter2.welho.com [::ffff:83.102.41.24]) (amavisd-new, port 10024) with ESMTP id dd99WkPMw4AE; Sun, 2 Oct 2016 20:19:10 +0300 (EEST)
Received: from LK-Perkele-V2 (87-100-237-87.bb.dnainternet.fi [87.100.237.87]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by welho-smtp2.welho.com (Postfix) with ESMTPSA id DFFAB21C; Sun, 2 Oct 2016 20:19:10 +0300 (EEST)
Date: Sun, 2 Oct 2016 20:19:05 +0300
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
Cc: Van Catha <vans554@gmail.com>, HTTP working group mailing list <ietf-http-wg@w3.org>
Message-ID: <20161002171905.GA10108@LK-Perkele-V2.elisa-laajakaista.fi>
References: <CAG-EYChPJpAzoEuNwY3cNz503d0FRbNnDx_9AsNsZyfb5nmN0g@mail.gmail.com> <20161002080030.5F328160CC@welho-filter4.welho.com> <20161002101548.GA9450@LK-Perkele-V2.elisa-laajakaista.fi> <201610021110.u92BAWpi019029@shell.siilo.fmi.fi> <20161002124346.GB9450@LK-Perkele-V2.elisa-laajakaista.fi> <201610021340.u92DeBBL029907@shell.siilo.fmi.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <201610021340.u92DeBBL029907@shell.siilo.fmi.fi>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: ilariliusvaara@welho.com
Received-SPF: none client-ip=83.102.41.24; envelope-from=ilariliusvaara@welho.com; helo=welho-filter2.welho.com
X-W3C-Hub-Spam-Status: No, score=-6.7
X-W3C-Hub-Spam-Report: AWL=-0.120, BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-2.641, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1bqkQN-000141-Bc 4d84126e99dc2aaa263c383107379235
X-Original-To: ietf-http-wg@w3.org
Subject: Re: WebSocket2
Archived-At: <http://www.w3.org/mid/20161002171905.GA10108@LK-Perkele-V2.elisa-laajakaista.fi>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32451
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Sun, Oct 02, 2016 at 04:40:11PM +0300, Kari Hurtta wrote:
> Ilari Liusvaara <ilariliusvaara@welho.com>om>: (Sun Oct  2 15:43:46 2016)
> > On Sun, Oct 02, 2016 at 02:10:32PM +0300, Kari Hurtta wrote:
> > > Ilari Liusvaara <ilariliusvaara@welho.com>om>: (Sun Oct  2 13:15:48 2016)
> > > > On Sun, Oct 02, 2016 at 11:00:29AM +0300, Kari hurtta wrote:
> > > > > 
> > > > > (A,B) Is there http  error code which tells that
> > > > > that it was unsuppoted :scheme (and not other 
> > > > > error, for example wrong :path) ?
> > > > > 
> > > > > That is needed that client (A) orPbroxy (B) can
> > > > > switch Websocket (RFC 6455) negotated over
> > > > > HTTP/1.1
> > > > 
> > > > I don't think there is (and that's a part of the problem) with current
> > > > scheme handling.
> > > > 
> > > > There are probably quite a bit of servers that just plain ignore the
> > > > scheme in request.
> > > 
> > > Hmm. Was reason why
> > > 
> > > https://tools.ietf.org/html/draft-hirano-httpbis-websocket-over-http2-01
> > > 
> > > used SETTINGS frame with SETTINGS_WEBSOCKET_CAPABLE parameter ?
> > > Seems not mention that reason. 
> > > 
> > > That means that server needs send SETTINGS_WEBSOCKET_CAPABLE = 1
> > > to client indicating that server handles :scheme = ws
> > > ( and on that draft SETTINGS_WEBSOCKET_CAPABLE = 1
> > >   was sent from client to server. )
> >  
> > Well, I think the following would work and avoid SETTINGS:
> > 
> > -> :method ws2
> > -> :scheme wss
> > -> :authority foo.example
> > -> :path /bar
> > -> <optional extra parameters, e.g. compression support>
> > <- :status 200
> > <- sec-ws2-ack 1
> > <- <optional negotiated extras>
> 
> If we can also assume that proxy does not ignore
>    :method = ws2
>    :scheme = ws
> then this may work.

Oh yeah, that only works against dodgily implemented origins, not WS2-
unsupporting proxies (that do something else than just realtime
forwarding of unknown methods).


If one is worried about the latter, one would need the SETTING then
(one only needs to have server end signal support, since it is a
capability server has that client may or may not use)..


-Ilari