W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

Re: Allow custom headers (Websocket API)

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 5 Feb 2015 14:57:06 +0100
Message-ID: <CADnb78iO2LHASqmHQ9zSfHEqAM=frE__xsWhQTpJTntFXBfvXw@mail.gmail.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: Florian Bösch <pyalot@gmail.com>, Michiel De Mey <de.mey.michiel@gmail.com>, WebApps WG <public-webapps@w3.org>
On Thu, Feb 5, 2015 at 2:48 PM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
> A Websocket connection is established by making a HTTP Upgrade request,
> and the protocol is HTTP unless and until the connection is upgraded.

Sure, but the server can get away with supporting a very limited
subset of HTTP, no? Anyway, perhaps a combination of a CORS preflight
followed by the HTTP Upgrade that then includes the headers is the
answer, would probably be best to ask some WebSocket library
developers what they think.


-- 
https://annevankesteren.nl/
Received on Thursday, 5 February 2015 13:57:30 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC