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

Re: Allow custom headers (Websocket API)

From: Michiel De Mey <de.mey.michiel@gmail.com>
Date: Thu, 5 Feb 2015 15:07:20 +0100
To: Anne van Kesteren <annevk@annevk.nl>, Takeshi Yoshino <tyoshino@google.com>
Cc: Florian Bösch <pyalot@gmail.com>, WebApps WG <public-webapps@w3.org>, Bjoern Hoehrmann <derhoermi@gmx.net>
Message-ID: <etPan.54d37919.436c6125.175@michiel.local>
Standardizing the approach would definitely help developers,  
however where will we communicate this?




On February 5, 2015 at 3:04:35 PM, Takeshi Yoshino (tyoshino@google.com) wrote:

On Thu, Feb 5, 2015 at 10:57 PM, Anne van Kesteren <annevk@annevk.nl> wrote:
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.

Agreed. Even if we don't make any change on the existing specs, we need to standardize (or just announce to developers) that they need to make servers understand that combination if they want to develop apps that uses custom headers. Then, client vendors could implement that.
 
Received on Thursday, 5 February 2015 14:07:51 UTC

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