web-dev-qa-db-fra.com

Websocket onerror - comment lire la description de l'erreur?

Je développe des jeux multi-joueurs basés sur un navigateur depuis un certain temps et je teste l’accessibilité de différents ports dans différents environnements (bureau du client, wifi public, etc.). Tout se passe plutôt bien, sauf une chose: je ne comprends pas comment lire l'erreur n °. ou une description du moment où un événement est reçu.

Le websocket du client se fait en javascript.

Par exemple:

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

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

'output' est juste une fonction utilitaire qui écrit dans un div.

Ce que je reçois est 'indéfini' pour ev.data. Toujours. Et j'ai cherché sur Google, mais il semble qu'il n'y ait aucune spécification sur les paramètres de cet événement et sur la façon de le lire correctement.

Toute aide est appréciée!

javascripthtml5websocket
64
Sinisa

L'erreur Event que le gestionnaire onerror reçoit est un simple événement ne contenant pas cette information :

Si l'agent utilisateur devait échouer la connexion WebSocket ou si la connexion WebSocket est fermée avec préjudice, déclenchez un événement simple nommé error sur l'objet WebSocket.

Vous aurez peut-être plus de chance d’écouter l’événement close, qui est un CloseEvent et a en effet un CloseEvent.code Propriété contenant un code numérique conforme à RFC 6455 11.7 et un CloseEvent.reason propriété de chaîne.

Veuillez noter cependant que CloseEvent.code (et CloseEvent.reason) sont limités de manière à éviter les problèmes de détection de réseau et autres problèmes de sécurité.

64
nmaier

A côté de la réponse de Nmaier, comme il l'a dit vous recevrez toujours le code 1006 . Cependant, si vous deviez théoriquement recevoir d'autres codes, voici le code pour afficher les résultats (via RFC6455 ).

vous n'obtiendrez presque jamais ces codes en pratique, donc ce code est plutôt inutile 

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();

Voir http://jsfiddle.net/gr0bhrqr/

77
Phylliida