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

[Bug 21147] WebSocket API could provide a method to get the HTTP response code when it's not 101

From: <bugzilla@jessica.w3.org>
Date: Mon, 04 Mar 2013 19:57:45 +0000
To: public-webapps@w3.org
Message-ID: <bug-21147-2927-WugzOg0X45@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21147

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|---                         |WONTFIX

--- Comment #7 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
That would be a bad way of doing things. If it's a WebSocket connection, use
the WebSocket protocol to send back the error, not HTTP. WebSocket isn't really
anything to de with HTTP, it just happens to be compatible for legacy reasons
(to make it easier to use one port with both protocols).

We can't expose stuff from arbitrary cross-origin HTTP servers. It would let
you do all kinds of things like intranet inspection, etc.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 4 March 2013 19:57:47 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT