Toggle Details

Autobahn WebSockets Testsuite Report
Autobahn WebSockets

Summary report generated on 2017-11-02T09:00:47Z (UTC) by Autobahn WebSockets Testsuite v0.5.5/v0.5.14.

Pass Test case was executed and passed successfully.
Non-Strict Test case was executed and passed non-strictly. A non-strict behavior is one that does not adhere to a SHOULD-behavior as described in the protocol specification or a well-defined, canonical behavior that appears to be desirable but left open in the protocol specification. An implementation with non-strict behavior is still conformant to the protocol specification.
Fail Test case was executed and failed. An implementation which fails a test case - other than a performance/limits related one - is non-conforming to a MUST-behavior as described in the protocol specification.
Info Informational test case which detects certain implementation behavior left unspecified by the spec but nevertheless potentially interesting to implementors.
Missing Test case is missing, either because it was skipped via the test suite configuration or deactivated, i.e. because the implementation does not implement the tested feature or breaks during running the test case.
1 Framing AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
1.1 Text Messages
Case 1.1.1 Pass1000 Pass1000 Pass1000
Case 1.1.2 Pass1000 Pass1000 Pass1000
Case 1.1.3 Pass1000 Pass1000 Pass1000
Case 1.1.4 Pass1000 Pass1000 Pass1000
Case 1.1.5 Pass1000 Pass1000 Pass1000
Case 1.1.6 Pass1000 Pass1000 Pass1000
Case 1.1.7 Pass1000 Pass1000 Pass1000
Case 1.1.8 Pass1000 Pass1000 Pass1000
1 Framing AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
1.2 Binary Messages
Case 1.2.1 Pass1000 Pass1000 Pass1000
Case 1.2.2 Pass1000 Pass1000 Pass1000
Case 1.2.3 Pass1000 Pass1000 Pass1000
Case 1.2.4 Pass1000 Pass1000 Pass1000
Case 1.2.5 Pass1000 Pass1000 Pass1000
Case 1.2.6 Pass1000 Pass1000 Pass1000
Case 1.2.7 Pass1000 Pass1000 Pass1000
Case 1.2.8 Pass1000 Pass1000 Pass1000
2 Pings/Pongs AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
Case 2.1 Pass1000 Pass1000 Pass1000
Case 2.2 Pass1000 Pass1000 Pass1000
Case 2.3 Pass1000 Pass1000 Pass1000
Case 2.4 Pass1000 Pass1000 Pass1000
Case 2.5 Pass1002 Pass1002 Pass1002
Case 2.6 Pass1000 Pass1000 Pass1000
Case 2.7 Pass1000 Pass1000 Pass1000
Case 2.8 Pass1000 Pass1000 Pass1000
Case 2.9 Pass1000 Pass1000 Pass1000
Case 2.10 Pass1000 Pass1000 Pass1000
Case 2.11 Pass1000 Pass1000 Pass1000
3 Reserved Bits AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
Case 3.1 Pass1002 Pass1002 Pass1002
Case 3.2 Pass1002 PassNone PassNone
Case 3.3 Pass1002 Pass1002 PassNone
Case 3.4 Pass1002 Pass1002 Pass1002
Case 3.5 Pass1002 Pass1002 Pass1002
Case 3.6 Pass1002 Pass1002 Pass1002
Case 3.7 PassNone Pass1002 Pass1002
4 Opcodes AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
4.1 Non-control Opcodes
Case 4.1.1 Pass1002 Pass1002 Pass1002
Case 4.1.2 Pass1002 Pass1002 Pass1002
Case 4.1.3 Pass1002 PassNone PassNone
Case 4.1.4 Pass1002 PassNone Pass1002
Case 4.1.5 Pass1002 Pass1002 Pass1002
4 Opcodes AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
4.2 Control Opcodes
Case 4.2.1 Pass1002 Pass1002 Pass1002
Case 4.2.2 Pass1002 Pass1002 Pass1002
Case 4.2.3 Pass1002 Pass1002 PassNone
Case 4.2.4 Pass1002 PassNone PassNone
Case 4.2.5 Pass1002 Pass1002 Pass1002
5 Fragmentation AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
Case 5.1 Pass1002 Pass1002 Pass1002
Case 5.2 Pass1002 Pass1002 Pass1002
Case 5.3 Pass1000 Pass1000 Pass1000
Case 5.4 Pass1000 Pass1000 Pass1000
Case 5.5 Pass1000 Pass1000 Pass1000
Case 5.6 Pass1000 Pass1000 Pass1000
Case 5.7 Pass1000 Pass1000 Pass1000
Case 5.8 Pass1000 Pass1000 Pass1000
Case 5.9 Pass1002 Pass1002 Pass1002
Case 5.10 Pass1002 Pass1002 Pass1002
Case 5.11 Pass1002 Pass1002 Pass1002
Case 5.12 Pass1002 Pass1002 Pass1002
Case 5.13 Pass1002 Pass1002 Pass1002
Case 5.14 Pass1002 Pass1002 Pass1002
Case 5.15 Pass1002 Pass1002 PassNone
Case 5.16 Pass1002 Pass1002 Pass1002
Case 5.17 Pass1002 Pass1002 Pass1002
Case 5.18 Pass1002 Pass1002 Pass1002
Case 5.19 Pass1000 Pass1000 Pass1000
Case 5.20 Pass1000 Pass1000 Pass1000
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.1 Valid UTF-8 with zero payload fragments
Case 6.1.1 Pass1000 Pass1000 Pass1000
Case 6.1.2 Pass1000 Pass1000 Pass1000
Case 6.1.3 Pass1000 Pass1000 Pass1000
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.2 Valid UTF-8 unfragmented, fragmented on code-points and within code-points
Case 6.2.1 Pass1000 Pass1000 Pass1000
Case 6.2.2 Pass1000 Pass1000 Pass1000
Case 6.2.3 Pass1000 Pass1000 Pass1000
Case 6.2.4 Pass1000 Pass1000 Pass1000
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.3 Invalid UTF-8 differently fragmented
Case 6.3.1 Pass1007 Pass1007 Pass1007
Case 6.3.2 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.4 Fail-fast on invalid UTF-8
Case 6.4.1 Pass1007 Pass1007 Pass1007
Case 6.4.2 Pass1007 Pass1007 Pass1007
Case 6.4.3 Pass1007 Pass1007 Pass1007
Case 6.4.4 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.5 Some valid UTF-8 sequences
Case 6.5.1 Pass1000 Pass1000 Pass1000
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.6 All prefixes of a valid UTF-8 string that contains multi-byte code points
Case 6.6.1 Pass1007 Pass1007 Pass1007
Case 6.6.2 Pass1000 Pass1000 Pass1000
Case 6.6.3 Pass1007 Pass1007 Pass1007
Case 6.6.4 Pass1007 Pass1007 Pass1007
Case 6.6.5 Pass1000 Pass1000 Pass1000
Case 6.6.6 Pass1007 Pass1007 Pass1007
Case 6.6.7 Pass1000 Pass1000 Pass1000
Case 6.6.8 Pass1007 Pass1007 Pass1007
Case 6.6.9 Pass1000 Pass1000 Pass1000
Case 6.6.10 Pass1007 Pass1007 Pass1007
Case 6.6.11 Pass1000 Pass1000 Pass1000
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.7 First possible sequence of a certain length
Case 6.7.1 Pass1000 Pass1000 Pass1000
Case 6.7.2 Pass1000 Pass1000 Pass1000
Case 6.7.3 Pass1000 Pass1000 Pass1000
Case 6.7.4 Pass1000 Pass1000 Pass1000
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.8 First possible sequence length 5/6 (invalid codepoints)
Case 6.8.1 Pass1007 Pass1007 Pass1007
Case 6.8.2 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.9 Last possible sequence of a certain length
Case 6.9.1 Pass1000 Pass1000 Pass1000
Case 6.9.2 Pass1000 Pass1000 Pass1000
Case 6.9.3 Pass1000 Pass1000 Pass1000
Case 6.9.4 Pass1000 Pass1000 Pass1000
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.10 Last possible sequence length 4/5/6 (invalid codepoints)
Case 6.10.1 Pass1007 Pass1007 Pass1007
Case 6.10.2 Pass1007 Pass1007 Pass1007
Case 6.10.3 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.11 Other boundary conditions
Case 6.11.1 Pass1000 Pass1000 Pass1000
Case 6.11.2 Pass1000 Pass1000 Pass1000
Case 6.11.3 Pass1000 Pass1000 Pass1000
Case 6.11.4 Pass1000 Pass1000 Pass1000
Case 6.11.5 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.12 Unexpected continuation bytes
Case 6.12.1 Pass1007 Pass1007 Pass1007
Case 6.12.2 Pass1007 Pass1007 Pass1007
Case 6.12.3 Pass1007 Pass1007 Pass1007
Case 6.12.4 Pass1007 Pass1007 Pass1007
Case 6.12.5 Pass1007 Pass1007 Pass1007
Case 6.12.6 Pass1007 Pass1007 Pass1007
Case 6.12.7 Pass1007 Pass1007 Pass1007
Case 6.12.8 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.13 Lonely start characters
Case 6.13.1 Pass1007 Pass1007 Pass1007
Case 6.13.2 Pass1007 Pass1007 Pass1007
Case 6.13.3 Pass1007 Pass1007 Pass1007
Case 6.13.4 Pass1007 Pass1007 Pass1007
Case 6.13.5 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.14 Sequences with last continuation byte missing
Case 6.14.1 Pass1007 Pass1007 Pass1007
Case 6.14.2 Pass1007 Pass1007 Pass1007
Case 6.14.3 Pass1007 Pass1007 Pass1007
Case 6.14.4 Pass1007 Pass1007 Pass1007
Case 6.14.5 Pass1007 Pass1007 Pass1007
Case 6.14.6 Pass1007 Pass1007 Pass1007
Case 6.14.7 Pass1007 Pass1007 Pass1007
Case 6.14.8 Pass1007 Pass1007 Pass1007
Case 6.14.9 Pass1007 Pass1007 Pass1007
Case 6.14.10 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.15 Concatenation of incomplete sequences
Case 6.15.1 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.16 Impossible bytes
Case 6.16.1 Pass1007 Pass1007 Pass1007
Case 6.16.2 Pass1007 Pass1007 Pass1007
Case 6.16.3 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.17 Examples of an overlong ASCII character
Case 6.17.1 Pass1007 Pass1007 Pass1007
Case 6.17.2 Pass1007 Pass1007 Pass1007
Case 6.17.3 Pass1007 Pass1007 Pass1007
Case 6.17.4 Pass1007 Pass1007 Pass1007
Case 6.17.5 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.18 Maximum overlong sequences
Case 6.18.1 Pass1007 Pass1007 Pass1007
Case 6.18.2 Pass1007 Pass1007 Pass1007
Case 6.18.3 Pass1007 Pass1007 Pass1007
Case 6.18.4 Pass1007 Pass1007 Pass1007
Case 6.18.5 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.19 Overlong representation of the NUL character
Case 6.19.1 Pass1007 Pass1007 Pass1007
Case 6.19.2 Pass1007 Pass1007 Pass1007
Case 6.19.3 Pass1007 Pass1007 Pass1007
Case 6.19.4 Pass1007 Pass1007 Pass1007
Case 6.19.5 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.20 Single UTF-16 surrogates
Case 6.20.1 Pass1007 Pass1007 Pass1007
Case 6.20.2 Pass1007 Pass1007 Pass1007
Case 6.20.3 Pass1007 Pass1007 Pass1007
Case 6.20.4 Pass1007 Pass1007 Pass1007
Case 6.20.5 Pass1007 Pass1007 Pass1007
Case 6.20.6 Pass1007 Pass1007 Pass1007
Case 6.20.7 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.21 Paired UTF-16 surrogates
Case 6.21.1 Pass1007 Pass1007 Pass1007
Case 6.21.2 Pass1007 Pass1007 Pass1007
Case 6.21.3 Pass1007 Pass1007 Pass1007
Case 6.21.4 Pass1007 Pass1007 Pass1007
Case 6.21.5 Pass1007 Pass1007 Pass1007
Case 6.21.6 Pass1007 Pass1007 Pass1007
Case 6.21.7 Pass1007 Pass1007 Pass1007
Case 6.21.8 Pass1007 Pass1007 Pass1007
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.22 Non-character code points (valid UTF-8)
Case 6.22.1 Pass1000 Pass1000 Pass1000
Case 6.22.2 Pass1000 Pass1000 Pass1000
Case 6.22.3 Pass1000 Pass1000 Pass1000
Case 6.22.4 Pass1000 Pass1000 Pass1000
Case 6.22.5 Pass1000 Pass1000 Pass1000
Case 6.22.6 Pass1000 Pass1000 Pass1000
Case 6.22.7 Pass1000 Pass1000 Pass1000
Case 6.22.8 Pass1000 Pass1000 Pass1000
Case 6.22.9 Pass1000 Pass1000 Pass1000
Case 6.22.10 Pass1000 Pass1000 Pass1000
Case 6.22.11 Pass1000 Pass1000 Pass1000
Case 6.22.12 Pass1000 Pass1000 Pass1000
Case 6.22.13 Pass1000 Pass1000 Pass1000
Case 6.22.14 Pass1000 Pass1000 Pass1000
Case 6.22.15 Pass1000 Pass1000 Pass1000
Case 6.22.16 Pass1000 Pass1000 Pass1000
Case 6.22.17 Pass1000 Pass1000 Pass1000
Case 6.22.18 Pass1000 Pass1000 Pass1000
Case 6.22.19 Pass1000 Pass1000 Pass1000
Case 6.22.20 Pass1000 Pass1000 Pass1000
Case 6.22.21 Pass1000 Pass1000 Pass1000
Case 6.22.22 Pass1000 Pass1000 Pass1000
Case 6.22.23 Pass1000 Pass1000 Pass1000
Case 6.22.24 Pass1000 Pass1000 Pass1000
Case 6.22.25 Pass1000 Pass1000 Pass1000
Case 6.22.26 Pass1000 Pass1000 Pass1000
Case 6.22.27 Pass1000 Pass1000 Pass1000
Case 6.22.28 Pass1000 Pass1000 Pass1000
Case 6.22.29 Pass1000 Pass1000 Pass1000
Case 6.22.30 Pass1000 Pass1000 Pass1000
Case 6.22.31 Pass1000 Pass1000 Pass1000
Case 6.22.32 Pass1000 Pass1000 Pass1000
Case 6.22.33 Pass1000 Pass1000 Pass1000
Case 6.22.34 Pass1000 Pass1000 Pass1000
6 UTF-8 Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
6.23 Unicode specials (i.e. replacement char)
Case 6.23.1 Pass1000 Pass1000 Pass1000
Case 6.23.2 Pass1000 Pass1000 Pass1000
Case 6.23.3 Pass1000 Pass1000 Pass1000
Case 6.23.4 Pass1000 Pass1000 Pass1000
Case 6.23.5 Pass1000 Pass1000 Pass1000
Case 6.23.6 Pass1000 Pass1000 Pass1000
Case 6.23.7 Pass1000 Pass1000 Pass1000
7 Close Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
7.1 Basic close behavior (fuzzer initiated)
Case 7.1.1 Pass1000 Pass1000 Pass1000
Case 7.1.2 Pass1000 Pass1000 Pass1000
Case 7.1.3 Pass1000 Pass1000 Pass1000
Case 7.1.4 Pass1000 Pass1000 Pass1000
Case 7.1.5 Pass1000 Pass1000 Pass1000
Case 7.1.6 Info1000 Info1000 Info1000
7 Close Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
7.3 Close frame structure: payload length (fuzzer initiated)
Case 7.3.1 Pass1000 Pass1000 Pass1000
Case 7.3.2 PassNone Pass1002 Pass1002
Case 7.3.3 Pass1000 Pass1000 Pass1000
Case 7.3.4 Pass1000 Pass1000 Pass1000
Case 7.3.5 Pass1000 Pass1000 Pass1000
Case 7.3.6 PassNone Pass1002 Pass1002
7 Close Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
7.5 Close frame structure: payload value (fuzzer initiated)
Case 7.5.1 PassNone Pass1007 Pass1007
7 Close Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
7.7 Close frame structure: valid close codes (fuzzer initiated)
Case 7.7.1 Pass1000 Pass1000 Pass1000
Case 7.7.2 Pass1000 Pass1000 Pass1000
Case 7.7.3 Pass1000 Pass1000 Pass1000
Case 7.7.4 Pass1000 Pass1000 Pass1000
Case 7.7.5 Pass1000 Pass1000 Pass1000
Case 7.7.6 Pass1000 Pass1000 Pass1000
Case 7.7.7 Pass1000 Pass1000 Pass1000
Case 7.7.8 Pass1000 Pass1000 Pass1000
Case 7.7.9 Pass1000 Pass1000 Pass1000
Case 7.7.10 Pass1000 Pass1000 Pass1000
Case 7.7.11 Pass1000 Pass1000 Pass1000
Case 7.7.12 Pass1000 Pass1000 Pass1000
Case 7.7.13 Pass1000 Pass1000 Pass1000
7 Close Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
7.9 Close frame structure: invalid close codes (fuzzer initiated)
Case 7.9.1 PassNone Pass1002 Pass1002
Case 7.9.2 PassNone Pass1002 Pass1002
Case 7.9.3 PassNone Pass1002 Pass1002
Case 7.9.4 PassNone Pass1002 Pass1002
Case 7.9.5 PassNone Pass1002 Pass1002
Case 7.9.6 PassNone Pass1002 Pass1002
Case 7.9.7 PassNone Pass1002 Pass1002
Case 7.9.8 PassNone Pass1002 Pass1002
Case 7.9.9 PassNone Pass1002 Pass1002
Case 7.9.10 PassNone Pass1002 Pass1002
Case 7.9.11 PassNone Pass1002 Pass1002
Case 7.9.12 PassNone Pass1002 Pass1002
Case 7.9.13 PassNone Pass1002 Pass1002
7 Close Handling AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
7.13 Informational close information (fuzzer initiated)
Case 7.13.1 InfoNone Info1002 Info1002
Case 7.13.2 InfoNone Info1002 Info1002
9 Limits/Performance AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
9.1 Text Message (increasing size)
Case 9.1.1 Pass
89 ms
1000 Pass
42 ms
1000 Pass
43 ms
1000
Case 9.1.2 Pass
337 ms
1000 Pass
165 ms
1000 Pass
167 ms
1000
Case 9.1.3 Pass
1443 ms
1000 Pass
652 ms
1000 Pass
661 ms
1000
Case 9.1.4 Pass
6429 ms
1000 Pass
2605 ms
1000 Pass
2642 ms
1000
Case 9.1.5 Pass
12471 ms
1000 Pass
5306 ms
1000 Pass
5265 ms
1000
Case 9.1.6 Pass
20920 ms
1000 Pass
10520 ms
1000 Pass
10626 ms
1000
9 Limits/Performance AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
9.2 Binary Message (increasing size)
Case 9.2.1 Pass
35 ms
1000 Pass
15 ms
1000 Pass
15 ms
1000
Case 9.2.2 Pass
129 ms
1000 Pass
57 ms
1000 Pass
58 ms
1000
Case 9.2.3 Pass
452 ms
1000 Pass
227 ms
1000 Pass
233 ms
1000
Case 9.2.4 Pass
1823 ms
1000 Pass
931 ms
1000 Pass
950 ms
1000
Case 9.2.5 Pass
3563 ms
1000 Pass
1831 ms
1000 Pass
1877 ms
1000
Case 9.2.6 Pass
7035 ms
1000 Pass
3745 ms
1000 Pass
3812 ms
1000
9 Limits/Performance AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
9.3 Fragmented Text Message (fixed size, increasing fragment size)
Case 9.3.1 Pass
8902 ms
1000 Pass
4352 ms
1000 Pass
4238 ms
1000
Case 9.3.2 Pass
5933 ms
1000 Pass
2988 ms
1000 Pass
2994 ms
1000
Case 9.3.3 Pass
5311 ms
1000 Pass
8508 ms
1000 Pass
2693 ms
1000
Case 9.3.4 Pass
5172 ms
1000 Pass
32206 ms
1000 Pass
2594 ms
1000
Case 9.3.5 Pass
5114 ms
1000 Pass
23661 ms
1000 Pass
2630 ms
1000
Case 9.3.6 Pass
5111 ms
1000 Pass
10823 ms
1000 Pass
2578 ms
1000
Case 9.3.7 Pass
5085 ms
1000 Pass
4745 ms
1000 Pass
2583 ms
1000
Case 9.3.8 Pass
5103 ms
1000 Pass
4003 ms
1000 Pass
2620 ms
1000
Case 9.3.9 Pass
5091 ms
1000 Pass
4100 ms
1000 Pass
2890 ms
1000
9 Limits/Performance AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
9.4 Fragmented Binary Message (fixed size, increasing fragment size)
Case 9.4.1 Pass
5317 ms
1000 Pass
4092 ms
1000 Pass
2552 ms
1000
Case 9.4.2 Pass
2538 ms
1000 Pass
2067 ms
1000 Pass
1383 ms
1000
Case 9.4.3 Pass
1897 ms
1000 Pass
1536 ms
1000 Pass
964 ms
1000
Case 9.4.4 Pass
1750 ms
1000 Pass
1390 ms
1000 Pass
898 ms
1000
Case 9.4.5 Pass
1719 ms
1000 Pass
1362 ms
1000 Pass
900 ms
1000
Case 9.4.6 Pass
1687 ms
1000 Pass
1346 ms
1000 Pass
936 ms
1000
Case 9.4.7 Pass
1693 ms
1000 Pass
1350 ms
1000 Pass
861 ms
1000
Case 9.4.8 Pass
1687 ms
1000 Pass
1350 ms
1000 Pass
867 ms
1000
Case 9.4.9 Pass
1671 ms
1000 Pass
1350 ms
1000 Pass
861 ms
1000
9 Limits/Performance AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
9.5 Text Message (fixed size, increasing chop size)
Case 9.5.1 Pass
17139 ms
1000 Pass
17427 ms
1000 Pass
17081 ms
1000
Case 9.5.2 Pass
8859 ms
1000 Pass
9205 ms
1000 Pass
8867 ms
1000
Case 9.5.3 Pass
4754 ms
1000 Pass
5098 ms
1000 Pass
4763 ms
1000
Case 9.5.4 Pass
2701 ms
1000 Pass
3036 ms
1000 Pass
2711 ms
1000
Case 9.5.5 Pass
1675 ms
1000 Pass
2009 ms
1000 Pass
1669 ms
1000
Case 9.5.6 Pass
1280 ms
1000 Pass
1492 ms
1000 Pass
1158 ms
1000
9 Limits/Performance AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
9.6 Binary Text Message (fixed size, increasing chop size)
Case 9.6.1 Pass
16652 ms
1000 Pass
16789 ms
1000 Pass
16678 ms
1000
Case 9.6.2 Pass
8439 ms
1000 Pass
8536 ms
1000 Pass
8433 ms
1000
Case 9.6.3 Pass
4335 ms
1000 Pass
4355 ms
1000 Pass
4329 ms
1000
Case 9.6.4 Pass
2277 ms
1000 Pass
2300 ms
1000 Pass
2280 ms
1000
Case 9.6.5 Pass
1252 ms
1000 Pass
1279 ms
1000 Pass
1252 ms
1000
Case 9.6.6 Pass
738 ms
1000 Pass
774 ms
1000 Pass
741 ms
1000
9 Limits/Performance AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
9.7 Text Message Roundtrip Time (fixed number, increasing size)
Case 9.7.1 Pass
191 ms
1000 Pass
145 ms
1000 Pass
125 ms
1000
Case 9.7.2 Pass
239 ms
1000 Pass
182 ms
1000 Pass
156 ms
1000
Case 9.7.3 Pass
322 ms
1000 Pass
214 ms
1000 Pass
193 ms
1000
Case 9.7.4 Pass
563 ms
1000 Pass
364 ms
1000 Pass
325 ms
1000
Case 9.7.5 Pass
1561 ms
1000 Pass
909 ms
1000 Pass
841 ms
1000
Case 9.7.6 Pass
5504 ms
1000 Pass
3099 ms
1000 Pass
2860 ms
1000
9 Limits/Performance AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
9.8 Binary Message Roundtrip Time (fixed number, increasing size)
Case 9.8.1 Pass
189 ms
1000 Pass
161 ms
1000 Pass
121 ms
1000
Case 9.8.2 Pass
221 ms
1000 Pass
171 ms
1000 Pass
140 ms
1000
Case 9.8.3 Pass
265 ms
1000 Pass
210 ms
1000 Pass
163 ms
1000
Case 9.8.4 Pass
354 ms
1000 Pass
269 ms
1000 Pass
217 ms
1000
Case 9.8.5 Pass
706 ms
1000 Pass
491 ms
1000 Pass
414 ms
1000
Case 9.8.6 Pass
2086 ms
1000 Pass
1265 ms
1000 Pass
1168 ms
1000
10 Misc AutobahnServer ServerFrameworkServer/6.6.5 ServerFrameworkServer/6.9
10.1 Auto-Fragmentation
Case 10.1.1 Pass1000 Pass1000 Pass1000



Case 1.1.1

Up

Case Description

Send text message with payload 0.

Case Expectation

Receive echo'ed text message (with empty payload). Clean close with normal code.


Case 1.1.2

Up

Case Description

Send text message message with payload of length 125.

Case Expectation

Receive echo'ed text message (with payload as sent). Clean close with normal code.


Case 1.1.3

Up

Case Description

Send text message message with payload of length 126.

Case Expectation

Receive echo'ed text message (with payload as sent). Clean close with normal code.


Case 1.1.4

Up

Case Description

Send text message message with payload of length 127.

Case Expectation

Receive echo'ed text message (with payload as sent). Clean close with normal code.


Case 1.1.5

Up

Case Description

Send text message message with payload of length 128.

Case Expectation

Receive echo'ed text message (with payload as sent). Clean close with normal code.


Case 1.1.6

Up

Case Description

Send text message message with payload of length 65535.

Case Expectation

Receive echo'ed text message (with payload as sent). Clean close with normal code.


Case 1.1.7

Up

Case Description

Send text message message with payload of length 65536.

Case Expectation

Receive echo'ed text message (with payload as sent). Clean close with normal code.


Case 1.1.8

Up

Case Description

Send text message message with payload of length 65536. Sent out data in chops of 997 octets.

Case Expectation

Receive echo'ed text message (with payload as sent). Clean close with normal code.


Case 1.2.1

Up

Case Description

Send binary message with payload 0.

Case Expectation

Receive echo'ed binary message (with empty payload). Clean close with normal code.


Case 1.2.2

Up

Case Description

Send binary message message with payload of length 125.

Case Expectation

Receive echo'ed binary message (with payload as sent). Clean close with normal code.


Case 1.2.3

Up

Case Description

Send binary message message with payload of length 126.

Case Expectation

Receive echo'ed binary message (with payload as sent). Clean close with normal code.


Case 1.2.4

Up

Case Description

Send binary message message with payload of length 127.

Case Expectation

Receive echo'ed binary message (with payload as sent). Clean close with normal code.


Case 1.2.5

Up

Case Description

Send binary message message with payload of length 128.

Case Expectation

Receive echo'ed binary message (with payload as sent). Clean close with normal code.


Case 1.2.6

Up

Case Description

Send binary message message with payload of length 65535.

Case Expectation

Receive echo'ed binary message (with payload as sent). Clean close with normal code.


Case 1.2.7

Up

Case Description

Send binary message message with payload of length 65536.

Case Expectation

Receive echo'ed binary message (with payload as sent). Clean close with normal code.


Case 1.2.8

Up

Case Description

Send binary message message with payload of length 65536. Sent out data in chops of 997 octets.

Case Expectation

Receive echo'ed binary message (with payload as sent). Clean close with normal code.


Case 2.1

Up

Case Description

Send ping without payload.

Case Expectation

Pong (with empty payload) is sent in reply to Ping. Clean close with normal code.


Case 2.2

Up

Case Description

Send ping with small text payload.

Case Expectation

Pong with payload echo'ed is sent in reply to Ping. Clean close with normal code.


Case 2.3

Up

Case Description

Send ping with small binary (non UTF-8) payload.

Case Expectation

Pong with payload echo'ed is sent in reply to Ping. Clean close with normal code.


Case 2.4

Up

Case Description

Send ping with binary payload of 125 octets.

Case Expectation

Pong with payload echo'ed is sent in reply to Ping. Clean close with normal code.


Case 2.5

Up

Case Description

Send ping with binary payload of 126 octets.

Case Expectation

Connection is failed immediately (1002/Protocol Error), since control frames are only allowed to have payload up to and including 125 octets..


Case 2.6

Up

Case Description

Send ping with binary payload of 125 octets, send in octet-wise chops.

Case Expectation

Pong with payload echo'ed is sent in reply to Ping. Implementations must be TCP clean. Clean close with normal code.


Case 2.7

Up

Case Description

Send unsolicited pong without payload. Verify nothing is received. Clean close with normal code.

Case Expectation

Nothing.


Case 2.8

Up

Case Description

Send unsolicited pong with payload. Verify nothing is received. Clean close with normal code.

Case Expectation

Nothing.


Case 2.9

Up

Case Description

Send unsolicited pong with payload. Send ping with payload. Verify pong for ping is received.

Case Expectation

Nothing in reply to own Pong, but Pong with payload echo'ed in reply to Ping. Clean close with normal code.


Case 2.10

Up

Case Description

Send 10 Pings with payload.

Case Expectation

Pongs for our Pings with all the payloads. Note: This is not required by the Spec .. but we check for this behaviour anyway. Clean close with normal code.


Case 2.11

Up

Case Description

Send 10 Pings with payload. Send out octets in octet-wise chops.

Case Expectation

Pongs for our Pings with all the payloads. Note: This is not required by the Spec .. but we check for this behaviour anyway. Clean close with normal code.


Case 3.1

Up

Case Description

Send small text message with RSV = 1.

Case Expectation

The connection is failed immediately (1002/protocol error), since RSV must be 0, when no extension defining RSV meaning has been negoiated.


Case 3.2

Up

Case Description

Send small text message, then send again with RSV = 2, then send Ping.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since RSV must be 0, when no extension defining RSV meaning has been negoiated. The Pong is not received.


Case 3.3

Up

Case Description

Send small text message, then send again with RSV = 3, then send Ping. Octets are sent in frame-wise chops. Octets are sent in octet-wise chops.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since RSV must be 0, when no extension defining RSV meaning has been negoiated. The Pong is not received.


Case 3.4

Up

Case Description

Send small text message, then send again with RSV = 4, then send Ping. Octets are sent in octet-wise chops.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since RSV must be 0, when no extension defining RSV meaning has been negoiated. The Pong is not received.


Case 3.5

Up

Case Description

Send small binary message with RSV = 5.

Case Expectation

The connection is failed immediately, since RSV must be 0.


Case 3.6

Up

Case Description

Send Ping with RSV = 6.

Case Expectation

The connection is failed immediately, since RSV must be 0.


Case 3.7

Up

Case Description

Send Close with RSV = 7.

Case Expectation

The connection is failed immediately, since RSV must be 0.


Case 4.1.1

Up

Case Description

Send frame with reserved non-control Opcode = 3.

Case Expectation

The connection is failed immediately.


Case 4.1.2

Up

Case Description

Send frame with reserved non-control Opcode = 4 and non-empty payload.

Case Expectation

The connection is failed immediately.


Case 4.1.3

Up

Case Description

Send small text message, then send frame with reserved non-control Opcode = 5, then send Ping.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.


Case 4.1.4

Up

Case Description

Send small text message, then send frame with reserved non-control Opcode = 6 and non-empty payload, then send Ping.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.


Case 4.1.5

Up

Case Description

Send small text message, then send frame with reserved non-control Opcode = 7 and non-empty payload, then send Ping.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.


Case 4.2.1

Up

Case Description

Send frame with reserved control Opcode = 11.

Case Expectation

The connection is failed immediately.


Case 4.2.2

Up

Case Description

Send frame with reserved control Opcode = 12 and non-empty payload.

Case Expectation

The connection is failed immediately.


Case 4.2.3

Up

Case Description

Send small text message, then send frame with reserved control Opcode = 13, then send Ping.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.


Case 4.2.4

Up

Case Description

Send small text message, then send frame with reserved control Opcode = 14 and non-empty payload, then send Ping.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.


Case 4.2.5

Up

Case Description

Send small text message, then send frame with reserved control Opcode = 15 and non-empty payload, then send Ping.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.


Case 5.1

Up

Case Description

Send Ping fragmented into 2 fragments.

Case Expectation

Connection is failed immediately, since control message MUST NOT be fragmented.


Case 5.2

Up

Case Description

Send Pong fragmented into 2 fragments.

Case Expectation

Connection is failed immediately, since control message MUST NOT be fragmented.


Case 5.3

Up

Case Description

Send text Message fragmented into 2 fragments.

Case Expectation

Message is processed and echo'ed back to us.


Case 5.4

Up

Case Description

Send text Message fragmented into 2 fragments, octets are sent in frame-wise chops.

Case Expectation

Message is processed and echo'ed back to us.


Case 5.5

Up

Case Description

Send text Message fragmented into 2 fragments, octets are sent in octet-wise chops.

Case Expectation

Message is processed and echo'ed back to us.


Case 5.6

Up

Case Description

Send text Message fragmented into 2 fragments, one ping with payload in-between.

Case Expectation

A pong is received, then the message is echo'ed back to us.


Case 5.7

Up

Case Description

Send text Message fragmented into 2 fragments, one ping with payload in-between. Octets are sent in frame-wise chops.

Case Expectation

A pong is received, then the message is echo'ed back to us.


Case 5.8

Up

Case Description

Send text Message fragmented into 2 fragments, one ping with payload in-between. Octets are sent in octet-wise chops.

Case Expectation

A pong is received, then the message is echo'ed back to us.


Case 5.9

Up

Case Description

Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in one chop.

Case Expectation

The connection is failed immediately, since there is no message to continue.


Case 5.10

Up

Case Description

Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in per-frame chops.

Case Expectation

The connection is failed immediately, since there is no message to continue.


Case 5.11

Up

Case Description

Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in octet-wise chops.

Case Expectation

The connection is failed immediately, since there is no message to continue.


Case 5.12

Up

Case Description

Send unfragmented Text Message after Continuation Frame with FIN = false, where there is nothing to continue, sent in one chop.

Case Expectation

The connection is failed immediately, since there is no message to continue.


Case 5.13

Up

Case Description

Send unfragmented Text Message after Continuation Frame with FIN = false, where there is nothing to continue, sent in per-frame chops.

Case Expectation

The connection is failed immediately, since there is no message to continue.


Case 5.14

Up

Case Description

Send unfragmented Text Message after Continuation Frame with FIN = false, where there is nothing to continue, sent in octet-wise chops.

Case Expectation

The connection is failed immediately, since there is no message to continue.


Case 5.15

Up

Case Description

Send text Message fragmented into 2 fragments, then Continuation Frame with FIN = false where there is nothing to continue, then unfragmented Text Message, all sent in one chop.

Case Expectation

The connection is failed immediately, since there is no message to continue.


Case 5.16

Up

Case Description

Repeated 2x: Continuation Frame with FIN = false (where there is nothing to continue), then text Message fragmented into 2 fragments.

Case Expectation

The connection is failed immediately, since there is no message to continue.


Case 5.17

Up

Case Description

Repeated 2x: Continuation Frame with FIN = true (where there is nothing to continue), then text Message fragmented into 2 fragments.

Case Expectation

The connection is failed immediately, since there is no message to continue.


Case 5.18

Up

Case Description

Send text Message fragmented into 2 fragments, with both frame opcodes set to text, sent in one chop.

Case Expectation

The connection is failed immediately, since all data frames after the initial data frame must have opcode 0.


Case 5.19

Up

Case Description

A fragmented text message is sent in multiple frames. After sending the first 2 frames of the text message, a Ping is sent. Then we wait 1s, then we send 2 more text fragments, another Ping and then the final text fragment. Everything is legal.

Case Expectation

The peer immediately answers the first Ping before it has received the last text message fragment. The peer pong's back the Ping's payload exactly, and echo's the payload of the fragmented message back to us.


Case 5.20

Up

Case Description

Same as Case 5.19, but send all frames with SYNC = True. Note, this does not change the octets sent in any way, only how the stream is chopped up on the wire.

Case Expectation

Same as Case 5.19. Implementations must be agnostic to how octet stream is chopped up on wire (must be TCP clean).


Case 6.1.1

Up

Case Description

Send text message of length 0.

Case Expectation

A message is echo'ed back to us (with empty payload).


Case 6.1.2

Up

Case Description

Send fragmented text message, 3 fragments each of length 0.

Case Expectation

A message is echo'ed back to us (with empty payload).


Case 6.1.3

Up

Case Description

Send fragmented text message, 3 fragments, first and last of length 0, middle non-empty.

Case Expectation

A message is echo'ed back to us (with payload = payload of middle fragment).


Case 6.2.1

Up

Case Description

Send a valid UTF-8 text message in one fragment.

MESSAGE:
Hello-µ@ßöäüàá-UTF-8!!
48656c6c6f2dc2b540c39fc3b6c3a4c3bcc3a0c3a12d5554462d382121

Case Expectation

The message is echo'ed back to us.


Case 6.2.2

Up

Case Description

Send a valid UTF-8 text message in two fragments, fragmented on UTF-8 code point boundary.

MESSAGE FRAGMENT 1:
Hello-µ@ßöä
48656c6c6f2dc2b540c39fc3b6c3a4

MESSAGE FRAGMENT 2:
üàá-UTF-8!!
c3bcc3a0c3a12d5554462d382121

Case Expectation

The message is echo'ed back to us.


Case 6.2.3

Up

Case Description

Send a valid UTF-8 text message in fragments of 1 octet, resulting in frames ending on positions which are not code point ends.

MESSAGE:
Hello-µ@ßöäüàá-UTF-8!!
48656c6c6f2dc2b540c39fc3b6c3a4c3bcc3a0c3a12d5554462d382121

Case Expectation

The message is echo'ed back to us.


Case 6.2.4

Up

Case Description

Send a valid UTF-8 text message in fragments of 1 octet, resulting in frames ending on positions which are not code point ends.

MESSAGE:
κόσμε
cebae1bdb9cf83cebcceb5

Case Expectation

The message is echo'ed back to us.


Case 6.3.1

Up

Case Description

Send invalid UTF-8 text message unfragmented.

MESSAGE:
cebae1bdb9cf83cebcceb5eda080656469746564

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.3.2

Up

Case Description

Send invalid UTF-8 text message in fragments of 1 octet, resulting in frames ending on positions which are not code point ends.

MESSAGE:
cebae1bdb9cf83cebcceb5eda080656469746564

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.4.1

Up

Case Description

Send invalid UTF-8 text message in 3 fragments (frames). First frame payload is valid, then wait, then 2nd frame which contains the payload making the sequence invalid, then wait, then 3rd frame with rest. Note that PART1 and PART3 are valid UTF-8 in themselves, PART2 is a 0x110000 encoded as in the UTF-8 integer encoding scheme, but the codepoint is invalid (out of range).

MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5
PART2 = f4908080
PART3 = 656469746564

Case Expectation

The first frame is accepted, we expect to timeout on the first wait. The 2nd frame should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.


Case 6.4.2

Up

Case Description

Same as Case 6.4.1, but in 2nd frame, we send only up to and including the octet making the complete payload invalid.

MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5f4
PART2 = 90
PART3 = 8080656469746564

Case Expectation

The first frame is accepted, we expect to timeout on the first wait. The 2nd frame should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.


Case 6.4.3

Up

Case Description

Same as Case 6.4.1, but we send message not in 3 frames, but in 3 chops of the same message frame.

MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5
PART2 = f4908080
PART3 = 656469746564

Case Expectation

The first chop is accepted, we expect to timeout on the first wait. The 2nd chop should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.


Case 6.4.4

Up

Case Description

Same as Case 6.4.2, but we send message not in 3 frames, but in 3 chops of the same message frame.

MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5f4
PART2 = 90
PART3 =

Case Expectation

The first chop is accepted, we expect to timeout on the first wait. The 2nd chop should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.


Case 6.5.1

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xcebae1bdb9cf83cebcceb5

Case Expectation

The message is echo'ed back to us.


Case 6.6.1

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xce

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.6.2

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xceba

Case Expectation

The message is echo'ed back to us.


Case 6.6.3

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xcebae1

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.6.4

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xcebae1bd

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.6.5

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xcebae1bdb9

Case Expectation

The message is echo'ed back to us.


Case 6.6.6

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xcebae1bdb9cf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.6.7

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xcebae1bdb9cf83

Case Expectation

The message is echo'ed back to us.


Case 6.6.8

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xcebae1bdb9cf83ce

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.6.9

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xcebae1bdb9cf83cebc

Case Expectation

The message is echo'ed back to us.


Case 6.6.10

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xcebae1bdb9cf83cebcce

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.6.11

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xcebae1bdb9cf83cebcceb5

Case Expectation

The message is echo'ed back to us.


Case 6.7.1

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0x00

Case Expectation

The message is echo'ed back to us.


Case 6.7.2

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xc280

Case Expectation

The message is echo'ed back to us.


Case 6.7.3

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xe0a080

Case Expectation

The message is echo'ed back to us.


Case 6.7.4

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf0908080

Case Expectation

The message is echo'ed back to us.


Case 6.8.1

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf888808080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.8.2

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xfc8480808080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.9.1

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0x7f

Case Expectation

The message is echo'ed back to us.


Case 6.9.2

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xdfbf

Case Expectation

The message is echo'ed back to us.


Case 6.9.3

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xefbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.9.4

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf48fbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.10.1

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf7bfbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.10.2

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xfbbfbfbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.10.3

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xfdbfbfbfbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.11.1

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xed9fbf

Case Expectation

The message is echo'ed back to us.


Case 6.11.2

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xee8080

Case Expectation

The message is echo'ed back to us.


Case 6.11.3

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xefbfbd

Case Expectation

The message is echo'ed back to us.


Case 6.11.4

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf48fbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.11.5

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf4908080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.12.1

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0x80

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.12.2

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.12.3

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0x80bf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.12.4

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0x80bf80

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.12.5

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0x80bf80bf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.12.6

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0x80bf80bf80

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.12.7

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0x80bf80bf80bf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.12.8

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0x808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9fa0a1a2a3a4a5a6a7a8a9aaabacadaeafb0b1b2b3b4b5b6b7b8b9babbbcbdbe

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.13.1

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xc020c120c220c320c420c520c620c720c820c920ca20cb20cc20cd20ce20cf20d020d120d220d320d420d520d620d720d820d920da20db20dc20dd20de20

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.13.2

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xe020e120e220e320e420e520e620e720e820e920ea20eb20ec20ed20ee20

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.13.3

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf020f120f220f320f420f520f620

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.13.4

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf820f920fa20

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.13.5

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xfc20

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.14.1

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xc0

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.14.2

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xe080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.14.3

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf08080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.14.4

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf8808080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.14.5

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xfc80808080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.14.6

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xdf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.14.7

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xefbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.14.8

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf7bfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.14.9

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xfbbfbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.14.10

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xfdbfbfbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.15.1

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xc0e080f08080f8808080fc80808080dfefbff7bfbffbbfbfbffdbfbfbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.16.1

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xfe

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.16.2

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xff

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.16.3

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xfefeffff

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.17.1

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xc0af

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.17.2

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xe080af

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.17.3

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf08080af

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.17.4

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf8808080af

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.17.5

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xfc80808080af

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.18.1

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xc1bf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.18.2

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xe09fbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.18.3

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf08fbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.18.4

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf887bfbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.18.5

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xfc83bfbfbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.19.1

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xc080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.19.2

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xe08080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.19.3

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf0808080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.19.4

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xf880808080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.19.5

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xfc8080808080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.20.1

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xeda080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.20.2

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xedadbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.20.3

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xedae80

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.20.4

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xedafbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.20.5

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xedb080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.20.6

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xedbe80

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.20.7

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xedbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.21.1

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xeda080edb080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.21.2

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xeda080edbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.21.3

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xedadbfedb080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.21.4

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xedadbfedbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.21.5

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xedae80edb080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.21.6

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xedae80edbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.21.7

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xedafbfedb080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.21.8

Up

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xedafbfedbfbf

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.


Case 6.22.1

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xefbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.2

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xefbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.3

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf09fbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.4

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf09fbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.5

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf0afbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.6

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf0afbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.7

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf0bfbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.8

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf0bfbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.9

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf18fbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.10

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf18fbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.11

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf19fbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.12

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf19fbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.13

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf1afbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.14

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf1afbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.15

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf1bfbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.16

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf1bfbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.17

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf28fbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.18

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf28fbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.19

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf29fbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.20

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf29fbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.21

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf2afbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.22

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf2afbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.23

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf2bfbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.24

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf2bfbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.25

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf38fbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.26

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf38fbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.27

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf39fbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.28

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf39fbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.29

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf3afbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.30

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf3afbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.31

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf3bfbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.32

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf3bfbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.22.33

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf48fbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.22.34

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xf48fbfbf

Case Expectation

The message is echo'ed back to us.


Case 6.23.1

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xefbfb9

Case Expectation

The message is echo'ed back to us.


Case 6.23.2

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xefbfba

Case Expectation

The message is echo'ed back to us.


Case 6.23.3

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xefbfbb

Case Expectation

The message is echo'ed back to us.


Case 6.23.4

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xefbfbc

Case Expectation

The message is echo'ed back to us.


Case 6.23.5

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xefbfbd

Case Expectation

The message is echo'ed back to us.


Case 6.23.6

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xefbfbe

Case Expectation

The message is echo'ed back to us.


Case 6.23.7

Up

Case Description

Send a text message with payload which is valid UTF-8 in one fragment.

Payload: 0xefbfbf

Case Expectation

The message is echo'ed back to us.


Case 7.1.1

Up

Case Description

Send a message followed by a close frame

Case Expectation

Echoed message followed by clean close with normal code.


Case 7.1.2

Up

Case Description

Send two close frames

Case Expectation

Clean close with normal code. Second close frame ignored.


Case 7.1.3

Up

Case Description

Send a ping after close message

Case Expectation

Clean close with normal code, no pong.


Case 7.1.4

Up

Case Description

Send text message after sending a close frame.

Case Expectation

Clean close with normal code. Text message ignored.


Case 7.1.5

Up

Case Description

Send message fragment1 followed by close then fragment

Case Expectation

Clean close with normal code.


Case 7.1.6

Up

Case Description

Send 256K message followed by close then a ping

Case Expectation

Case outcome depends on implimentation defined close behavior. Message and close frame are sent back to back. If the close frame is processed before the text message write is complete (as can happen in asyncronous processing models) the close frame is processed first and the text message may not be recieved or may only be partially recieved.


Case 7.3.1

Up

Case Description

Send a close frame with payload length 0 (no close code, no close reason)

Case Expectation

Clean close with normal code.


Case 7.3.2

Up

Case Description

Send a close frame with payload length 1

Case Expectation

Clean close with protocol error or drop TCP.


Case 7.3.3

Up

Case Description

Send a close frame with payload length 2 (regular close with a code)

Case Expectation

Clean close with normal code.


Case 7.3.4

Up

Case Description

Send a close frame with close code and close reason

Case Expectation

Clean close with normal code.


Case 7.3.5

Up

Case Description

Send a close frame with close code and close reason of maximum length (123)

Case Expectation

Clean close with normal code.


Case 7.3.6

Up

Case Description

Send a close frame with close code and close reason which is too long (124) - total frame payload 126 octets

Case Expectation

Clean close with protocol error code or dropped TCP connection.


Case 7.5.1

Up

Case Description

Send a close frame with invalid UTF8 payload

Case Expectation

Clean close with protocol error or invalid utf8 code or dropped TCP.


Case 7.7.1

Up

Case Description

Send close with valid close code 1000

Case Expectation

Clean close with normal or echoed code


Case 7.7.2

Up

Case Description

Send close with valid close code 1001

Case Expectation

Clean close with normal or echoed code


Case 7.7.3

Up

Case Description

Send close with valid close code 1002

Case Expectation

Clean close with normal or echoed code


Case 7.7.4

Up

Case Description

Send close with valid close code 1003

Case Expectation

Clean close with normal or echoed code


Case 7.7.5

Up

Case Description

Send close with valid close code 1007

Case Expectation

Clean close with normal or echoed code


Case 7.7.6

Up

Case Description

Send close with valid close code 1008

Case Expectation

Clean close with normal or echoed code


Case 7.7.7

Up

Case Description

Send close with valid close code 1009

Case Expectation

Clean close with normal or echoed code


Case 7.7.8

Up

Case Description

Send close with valid close code 1010

Case Expectation

Clean close with normal or echoed code


Case 7.7.9

Up

Case Description

Send close with valid close code 1011

Case Expectation

Clean close with normal or echoed code


Case 7.7.10

Up

Case Description

Send close with valid close code 3000

Case Expectation

Clean close with normal or echoed code


Case 7.7.11

Up

Case Description

Send close with valid close code 3999

Case Expectation

Clean close with normal or echoed code


Case 7.7.12

Up

Case Description

Send close with valid close code 4000

Case Expectation

Clean close with normal or echoed code


Case 7.7.13

Up

Case Description

Send close with valid close code 4999

Case Expectation

Clean close with normal or echoed code


Case 7.9.1

Up

Case Description

Send close with invalid close code 0

Case Expectation

Clean close with protocol error code or drop TCP


Case 7.9.2

Up

Case Description

Send close with invalid close code 999

Case Expectation

Clean close with protocol error code or drop TCP


Case 7.9.3

Up

Case Description

Send close with invalid close code 1004

Case Expectation

Clean close with protocol error code or drop TCP


Case 7.9.4

Up

Case Description

Send close with invalid close code 1005

Case Expectation

Clean close with protocol error code or drop TCP


Case 7.9.5

Up

Case Description

Send close with invalid close code 1006

Case Expectation

Clean close with protocol error code or drop TCP


Case 7.9.6

Up

Case Description

Send close with invalid close code 1012

Case Expectation

Clean close with protocol error code or drop TCP


Case 7.9.7

Up

Case Description

Send close with invalid close code 1013

Case Expectation

Clean close with protocol error code or drop TCP


Case 7.9.8

Up

Case Description

Send close with invalid close code 1014

Case Expectation

Clean close with protocol error code or drop TCP


Case 7.9.9

Up

Case Description

Send close with invalid close code 1015

Case Expectation

Clean close with protocol error code or drop TCP


Case 7.9.10

Up

Case Description

Send close with invalid close code 1016

Case Expectation

Clean close with protocol error code or drop TCP


Case 7.9.11

Up

Case Description

Send close with invalid close code 1100

Case Expectation

Clean close with protocol error code or drop TCP


Case 7.9.12

Up

Case Description

Send close with invalid close code 2000

Case Expectation

Clean close with protocol error code or drop TCP


Case 7.9.13

Up

Case Description

Send close with invalid close code 2999

Case Expectation

Clean close with protocol error code or drop TCP


Case 7.13.1

Up

Case Description

Send close with close code 5000

Case Expectation

Actual events are undefined by the spec.


Case 7.13.2

Up

Case Description

Send close with close code 65536

Case Expectation

Actual events are undefined by the spec.


Case 9.1.1

Up

Case Description

Send text message message with payload of length 64 * 2**10 (64k).

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.1.2

Up

Case Description

Send text message message with payload of length 256 * 2**10 (256k).

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.1.3

Up

Case Description

Send text message message with payload of length 1 * 2**20 (1M).

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.1.4

Up

Case Description

Send text message message with payload of length 4 * 2**20 (4M).

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.1.5

Up

Case Description

Send text message message with payload of length 8 * 2**20 (8M).

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.1.6

Up

Case Description

Send text message message with payload of length 16 * 2**20 (16M).

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.2.1

Up

Case Description

Send binary message message with payload of length 64 * 2**10 (64k).

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.2.2

Up

Case Description

Send binary message message with payload of length 256 * 2**10 (256k).

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.2.3

Up

Case Description

Send binary message message with payload of length 1 * 2**20 (1M).

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.2.4

Up

Case Description

Send binary message message with payload of length 4 * 2**20 (4M).

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.2.5

Up

Case Description

Send binary message message with payload of length 8 * 2**20 (16M).

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.2.6

Up

Case Description

Send binary message message with payload of length 16 * 2**20 (16M).

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.3.1

Up

Case Description

Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 64.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.3.2

Up

Case Description

Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 256.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.3.3

Up

Case Description

Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 1k.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.3.4

Up

Case Description

Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 4k.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.3.5

Up

Case Description

Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 16k.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.3.6

Up

Case Description

Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 64k.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.3.7

Up

Case Description

Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 256k.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.3.8

Up

Case Description

Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 1M.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.3.9

Up

Case Description

Send fragmented text message message with message payload of length 4 * 2**20 (8M). Sent out in fragments of 4M.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.4.1

Up

Case Description

Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 64.

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.4.2

Up

Case Description

Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 256.

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.4.3

Up

Case Description

Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 1k.

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.4.4

Up

Case Description

Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 4k.

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.4.5

Up

Case Description

Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 16k.

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.4.6

Up

Case Description

Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 64k.

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.4.7

Up

Case Description

Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 256k.

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.4.8

Up

Case Description

Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 1M.

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.4.9

Up

Case Description

Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 4M.

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.5.1

Up

Case Description

Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 64 octets.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.5.2

Up

Case Description

Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 128 octets.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.5.3

Up

Case Description

Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 256 octets.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.5.4

Up

Case Description

Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 512 octets.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.5.5

Up

Case Description

Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 1024 octets.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.5.6

Up

Case Description

Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 2048 octets.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.6.1

Up

Case Description

Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 64 octets.

Case Expectation

Receive echo'ed binary message (with payload as sent).


Case 9.6.2

Up

Case Description

Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 128 octets.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.6.3

Up

Case Description

Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 256 octets.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.6.4

Up

Case Description

Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 512 octets.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.6.5

Up

Case Description

Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 1024 octets.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.6.6

Up

Case Description

Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 2048 octets.

Case Expectation

Receive echo'ed text message (with payload as sent).


Case 9.7.1

Up

Case Description

Send 1000 text messages of payload size 0 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed text messages (with payload as sent). Timeout case after 60 secs.


Case 9.7.2

Up

Case Description

Send 1000 text messages of payload size 16 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed text messages (with payload as sent). Timeout case after 60 secs.


Case 9.7.3

Up

Case Description

Send 1000 text messages of payload size 64 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed text messages (with payload as sent). Timeout case after 60 secs.


Case 9.7.4

Up

Case Description

Send 1000 text messages of payload size 256 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed text messages (with payload as sent). Timeout case after 120 secs.


Case 9.7.5

Up

Case Description

Send 1000 text messages of payload size 1024 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed text messages (with payload as sent). Timeout case after 240 secs.


Case 9.7.6

Up

Case Description

Send 1000 text messages of payload size 4096 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed text messages (with payload as sent). Timeout case after 480 secs.


Case 9.8.1

Up

Case Description

Send 1000 binary messages of payload size 0 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed binary messages (with payload as sent). Timeout case after 60 secs.


Case 9.8.2

Up

Case Description

Send 1000 binary messages of payload size 16 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed binary messages (with payload as sent). Timeout case after 60 secs.


Case 9.8.3

Up

Case Description

Send 1000 binary messages of payload size 64 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed binary messages (with payload as sent). Timeout case after 60 secs.


Case 9.8.4

Up

Case Description

Send 1000 binary messages of payload size 256 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed binary messages (with payload as sent). Timeout case after 120 secs.


Case 9.8.5

Up

Case Description

Send 1000 binary messages of payload size 1024 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed binary messages (with payload as sent). Timeout case after 240 secs.


Case 9.8.6

Up

Case Description

Send 1000 binary messages of payload size 4096 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed binary messages (with payload as sent). Timeout case after 480 secs.


Case 10.1.1

Up

Case Description

Send text message with payload of length 65536 auto-fragmented with autoFragmentSize = 1300.

Case Expectation

Receive echo'ed text message (with payload as sent and transmitted frame counts as expected). Clean close with normal code.