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:29:29 +0100
Message-ID: <CADnb78hXizhyrFoGVjPf_7wJks1f6OOFJL6jutVJQ1Vmpg3DuA@mail.gmail.com>
To: Florian Bösch <pyalot@gmail.com>
Cc: Michiel De Mey <de.mey.michiel@gmail.com>, WebApps WG <public-webapps@w3.org>
On Thu, Feb 5, 2015 at 2:23 PM, Florian Bösch <pyalot@gmail.com> wrote:
> 2) Clients do not apply CORS to WebSocket requests, and you're screwed,
> because any change you make will break existing deployments.

We can roll out a revision to the protocol that supports some kind of
CORS-like prefetching mechanism to opt into custom headers just fine I
think. Just requires some set of people to do the work.


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

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