- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Sun, 29 Oct 2017 09:37:09 +0100
- To: Patrick McManus <pmcmanus@mozilla.com>
- Cc: John Fallows <john.fallows@kaazing.com>, hybi <hybi@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
On Fri, Oct 27, 2017 at 7:13 PM, Patrick McManus <pmcmanus@mozilla.com> wrote: > I'm not changing the scheme. It was also wss in http/1.1 as well - its just that scheme does not typically appear on the wire in that protocol. My reference to 7540 8.1.2.3 explicitly talks about non http schemes (ftp is the most common). That doesn't make CONNECT/TUNNEL non http.. it just means http is being used to interact with a non-http service.. FWIW, we do change the scheme from the API perspective: https://fetch.spec.whatwg.org/#websocket-protocol (details in section 6.2). The reason for that is 1) the handshake is a simple HTTP request 2) it makes it a lot easier to share HSTS, CSP, Mixed Content logic, etc. So by the time it gets to the protocol there's no ws/wss. I think ws/wss was largely a legacy thing from when we still thought it wouldn't require HTTP at all. -- https://annevankesteren.nl/
Received on Sunday, 29 October 2017 08:37:34 UTC