W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2016

Re: WebSocket2

From: Kari hurtta <hurtta-ietf@elmme-mailer.org>
Date: Sun, 2 Oct 2016 11:00:29 +0300 (EEST)
To: Van Catha <vans554@gmail.com>, HTTP working group mailing list <ietf-http-wg@w3.org>
CC: Ilari Liusvaara <ilariliusvaara@welho.com>, Kari hurtta <hurtta-ietf@elmme-mailer.org>
Message-Id: <20161002080030.5F328160CC@welho-filter4.welho.com>

> So in the current state of affairs, using wss as the scheme over HTTP/2
> will default to using
> WebSocket2. Using ws as the scheme will default to WebSocket2 as well (for
> backwards compat).
> So if the client API uses WebSocket("ws://my-http2-server.com/channel") or
> wss, both should
> go to WebSocket2.
> Where is the problem in HTTP/2 that would disallow schemes different from
> http and https, I do not see
> anything related to this?

So your client does HTTP/2
request with 


• If proxy does not support "ws" then it respons with error page,
  so you are negotating Websockect over HTTP/2 (as I hope).


• If proxy supports "ws", and next hop does not support HTTP/2
  then proxy uses 

The WebSocket Protocol

• If proxy supports "ws", and next hop supports HTTP/2,
then proxy does HTTP/2
request with


   If next hop (probably origin server), does not
   support "ws" then it respons with error page


(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

/ Kari Hurtta
Received on Sunday, 2 October 2016 08:01:03 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 2 October 2016 08:01:07 UTC