Content - de8f51f28c6b70b2e2965198be18f242112ae556 - a76c33c/websockets/Secure-Close-1005.htm

visit type:

Tip revision: af678273b4059c687242b7a2bc1ebacffd1750c9 authored by Geoffrey Sneddon on 27 March 2018, 15:21:52 UTC
Move the config into its own class

Tip revision: af67827

Secure-Close-1005.htm

<!DOCTYPE html>
<html>
<head>
    <title>W3C WebSocket API - Close Secure WebSocket - Code is 1005</title>
    <script type="text/javascript" src="/resources/testharness.js"></script>
    <script type="text/javascript" src="/resources/testharnessreport.js"></script>
    <script type="text/javascript" src="websocket.sub.js"></script>
</head>
<body>
    <div id="log"></div>
    <script type="text/javascript">

        var test = async_test("W3C WebSocket API - Create Secure WebSocket - Close the Connection - close(1005) - see '7.1.5.  The WebSocket Connection Close Code' in http://www.ietf.org/rfc/rfc6455.txt");

        var wsocket = CreateWebSocket(true, false, false);
        var isOpenCalled = false;

        wsocket.addEventListener('open', test.step_func(function (evt) {
            assert_throws("INVALID_ACCESS_ERR", function () { wsocket.close(1005, "1005 - reserved code") });
            test.done();
        }), true);
    </script>

</body>
</html>

Browse the archive

https://github.com/web-platform-tests/wpt