Question

我一直在开发基于浏览器的多人游戏一段时间，我一直在各种环境（客户办公室，公共wifi等）测试不同的端口可访问性。一切都很顺利，除了一件事：我无法弄清楚如何读取错误号。或收到恐怖事件时的描述。

客户端websocket在javascript中完成。

例如：

// Init of websocket
websocket = new WebSocket(wsUri);
websocket.onerror = OnSocketError;
...etc...

// Handler for onerror:
function OnSocketError(ev)
{
    output("Socket error: " + ev.data);
}

'output'只是一些写入div的实用函数。

我得到的是ev.data的'undefined'。总是。我一直在谷歌搜索，但似乎没有关于这个事件有什么参数以及如何正确阅读它的规范。

感谢任何帮助！

Answer 1

除了nmaier的回答，正如他所说you'll always receive code 1006。但是，如果您理论上以某种方式接收其他代码，则此处是显示结果的代码（通过RFC6455）。

您几乎从未在实践中获得这些代码，因此此代码几乎毫无意义

var websocket;
if ("WebSocket" in window)
{
    websocket = new WebSocket("ws://yourDomainNameHere.org/");

    websocket.onopen = function (event) {
        $("#thingsThatHappened").html($("#thingsThatHappened").html() + "<br />" + "The connection was opened");
    };
    websocket.onclose = function (event) {
        var reason;
        alert(event.code);
        // See http://tools.ietf.org/html/rfc6455#section-7.4.1
        if (event.code == 1000)
            reason = "Normal closure, meaning that the purpose for which the connection was established has been fulfilled.";
        else if(event.code == 1001)
            reason = "An endpoint is \"going away\", such as a server going down or a browser having navigated away from a page.";
        else if(event.code == 1002)
            reason = "An endpoint is terminating the connection due to a protocol error";
        else if(event.code == 1003)
            reason = "An endpoint is terminating the connection because it has received a type of data it cannot accept (e.g., an endpoint that understands only text data MAY send this if it receives a binary message).";
        else if(event.code == 1004)
            reason = "Reserved. The specific meaning might be defined in the future.";
        else if(event.code == 1005)
            reason = "No status code was actually present.";
        else if(event.code == 1006)
           reason = "The connection was closed abnormally, e.g., without sending or receiving a Close control frame";
        else if(event.code == 1007)
            reason = "An endpoint is terminating the connection because it has received data within a message that was not consistent with the type of the message (e.g., non-UTF-8 [http://tools.ietf.org/html/rfc3629] data within a text message).";
        else if(event.code == 1008)
            reason = "An endpoint is terminating the connection because it has received a message that \"violates its policy\". This reason is given either if there is no other sutible reason, or if there is a need to hide specific details about the policy.";
        else if(event.code == 1009)
           reason = "An endpoint is terminating the connection because it has received a message that is too big for it to process.";
        else if(event.code == 1010) // Note that this status code is not used by the server, because it can fail the WebSocket handshake instead.
            reason = "An endpoint (client) is terminating the connection because it has expected the server to negotiate one or more extension, but the server didn't return them in the response message of the WebSocket handshake. <br /> Specifically, the extensions that are needed are: " + event.reason;
        else if(event.code == 1011)
            reason = "A server is terminating the connection because it encountered an unexpected condition that prevented it from fulfilling the request.";
        else if(event.code == 1015)
            reason = "The connection was closed due to a failure to perform a TLS handshake (e.g., the server certificate can't be verified).";
        else
            reason = "Unknown reason";

        $("#thingsThatHappened").html($("#thingsThatHappened").html() + "<br />" + "The connection was closed for reason: " + reason);
    };
    websocket.onmessage = function (event) {
        $("#thingsThatHappened").html($("#thingsThatHappened").html() + "<br />" + "New message arrived: " + event.data);
    };
    websocket.onerror = function (event) {
        $("#thingsThatHappened").html($("#thingsThatHappened").html() + "<br />" + "There was an error with your websocket.");
    };
}
else
{
    alert("Websocket is not supported by your browser");
    return;
}

websocket.send("Yo wazzup");

websocket.close();

请参阅http://jsfiddle.net/gr0bhrqr/

Answer 2

Event处理程序错误onerror收到is a simple event not containing such information：

如果要求用户代理失败WebSocket连接或者使用偏见关闭WebSocket连接，则在WebSocket对象上触发一个名为error的简单事件。

您可能会更好地收听close事件，这是一个CloseEvent，确实有一个CloseEvent.code属性，其中包含根据RFC 6455 11.7和{{{}}的数字代码{1}}字符串属性。

但请注意CloseEvent.reason（和CloseEvent.code）are limited，以避免网络探测和其他安全问题。

Answer 3

对于那些把谨慎抛诸脑后的人来说，潜在的愚蠢修复：返回一个状态代码。通过访问处理程序接收到的参数的 onerror 属性，可以从 message 事件处理程序查看状态代码。我建议使用 440 年代 - 似乎是免费的房地产。

“意外的服务器响应：440”

一点正则表达式就可以解决问题：

const socket = new WebSocket(/* yuh */);

socket.onerror = e => {
  const errorCode = e.message.match(/\d{3}/)[0];
  // errorCode = '440'
  // make your own rudimentary standard for error codes and handle them accordingly
};

在紧要关头可能会有用，但不要因为任何不可预见的影响向我哭泣。

Websocket onerror - 如何读取错误描述？

3 个答案:

您几乎从未在实践中获得这些代码，因此此代码几乎毫无意义

“意外的服务器响应：440”