- From: <bugzilla@jessica.w3.org>
- Date: Thu, 28 Feb 2013 21:03:49 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21147 --- Comment #2 from I <ibc@aliax.net> --- Well, the browser console already shows the HTTP status code of the non 101 response, but the JavaScript application can not get it. What I consider useful is that the JS code can get the HTTP status code to inform the user (for example 403 could mean "You are not authorized to connect to this WebSocket server"). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 28 February 2013 21:03:51 UTC