Toggle Details

Autobahn WebSockets Testsuite Report
Autobahn WebSockets

Summary report generated on 2012-10-12T12:42:25Z (UTC) by Autobahn WebSockets Testsuite v0.5.2/v0.5.8.

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 AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
1.1 Text Messages
Case 1.1.1 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.1.2 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.1.3 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.1.4 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.1.5 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.1.6 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.1.7 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.1.8 Pass1000 PassNone Pass1000 PassNone Pass1000
1 Framing AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
1.2 Binary Messages
Case 1.2.1 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.2.2 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.2.3 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.2.4 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.2.5 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.2.6 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.2.7 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 1.2.8 Pass1000 PassNone Pass1000 PassNone Pass1000
2 Pings/Pongs AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
Case 2.1 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 2.2 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 2.3 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 2.4 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 2.5 Pass1002 PassNone PassNone PassNone Pass1002
Case 2.6 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 2.7 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 2.8 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 2.9 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 2.10 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 2.11 Pass1000 PassNone Pass1000 PassNone Pass1000
3 Reserved Bits AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
Case 3.1 Pass1002 PassNone PassNone PassNone Pass1002
Case 3.2 Pass1002 PassNone Non-StrictNone PassNone Pass1002
Case 3.3 Pass1002 PassNone Non-StrictNone PassNone Pass1002
Case 3.4 Pass1002 PassNone PassNone PassNone Pass1002
Case 3.5 Pass1002 PassNone PassNone PassNone Pass1002
Case 3.6 Pass1002 PassNone PassNone PassNone Pass1002
Case 3.7 Pass1002 PassNone PassNone PassNone Pass1002
4 Opcodes AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
4.1 Non-control Opcodes
Case 4.1.1 Pass1002 PassNone PassNone PassNone Pass1002
Case 4.1.2 Pass1002 PassNone PassNone PassNone Pass1002
Case 4.1.3 Pass1002 PassNone Non-StrictNone PassNone Pass1002
Case 4.1.4 Pass1002 PassNone Non-StrictNone PassNone Pass1002
Case 4.1.5 Pass1002 PassNone PassNone PassNone Pass1002
4 Opcodes AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
4.2 Control Opcodes
Case 4.2.1 Pass1002 PassNone PassNone PassNone Pass1002
Case 4.2.2 Pass1002 PassNone PassNone PassNone Pass1002
Case 4.2.3 Pass1002 PassNone Non-StrictNone PassNone Pass1002
Case 4.2.4 Pass1002 PassNone Non-StrictNone PassNone Pass1002
Case 4.2.5 Pass1002 PassNone PassNone PassNone Pass1002
5 Fragmentation AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
Case 5.1 Pass1002 PassNone PassNone PassNone Pass1002
Case 5.2 Pass1002 PassNone PassNone PassNone Pass1002
Case 5.3 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 5.4 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 5.5 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 5.6 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 5.7 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 5.8 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 5.9 Pass1002 PassNone PassNone PassNone Pass1002
Case 5.10 Pass1002 PassNone PassNone PassNone Pass1002
Case 5.11 Pass1002 PassNone PassNone PassNone Pass1002
Case 5.12 Pass1002 PassNone PassNone PassNone Pass1002
Case 5.13 Pass1002 PassNone PassNone PassNone Pass1002
Case 5.14 Pass1002 PassNone PassNone PassNone Pass1002
Case 5.15 Pass1002 PassNone Non-StrictNone PassNone Pass1002
Case 5.16 Pass1002 PassNone PassNone PassNone Pass1002
Case 5.17 Pass1002 PassNone PassNone PassNone Pass1002
Case 5.18 Pass1002 PassNone PassNone PassNone Pass1002
Case 5.19 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 5.20 Pass1000 PassNone Pass1000 PassNone Pass1000
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.1 Valid UTF-8 with zero payload fragments
Case 6.1.1 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.1.2 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.1.3 Pass1000 PassNone Pass1000 PassNone Pass1000
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.2 Valid UTF-8 unfragmented, fragmented on code-points and within code-points
Case 6.2.1 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.2.2 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.2.3 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.2.4 Pass1000 PassNone Pass1000 PassNone Pass1000
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.3 Invalid UTF-8 differently fragmented
Case 6.3.1 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.3.2 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.4 Fail-fast on invalid UTF-8
Case 6.4.1 Pass1007 Non-StrictNone Non-StrictNone Non-StrictNone Pass1007
Case 6.4.2 Pass1007 Non-StrictNone Non-StrictNone Non-StrictNone Pass1007
Case 6.4.3 Pass1007 Non-StrictNone Non-StrictNone Non-StrictNone Pass1007
Case 6.4.4 Pass1007 Non-StrictNone Non-StrictNone Non-StrictNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.5 Some valid UTF-8 sequences
Case 6.5.1 Pass1000 PassNone Pass1000 PassNone Pass1000
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.6 All prefixes of a valid UTF-8 string that contains multi-byte code points
Case 6.6.1 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.6.2 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.6.3 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.6.4 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.6.5 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.6.6 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.6.7 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.6.8 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.6.9 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.6.10 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.6.11 Pass1000 PassNone Pass1000 PassNone Pass1000
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.7 First possible sequence of a certain length
Case 6.7.1 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.7.2 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.7.3 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.7.4 Pass1000 PassNone Pass1000 PassNone Pass1000
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.8 First possible sequence length 5/6 (invalid codepoints)
Case 6.8.1 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.8.2 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.9 Last possible sequence of a certain length
Case 6.9.1 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.9.2 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.9.3 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.9.4 Pass1000 PassNone Pass1000 PassNone Pass1000
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.10 Last possible sequence length 4/5/6 (invalid codepoints)
Case 6.10.1 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.10.2 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.10.3 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.11 Other boundary conditions
Case 6.11.1 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.11.2 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.11.3 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.11.4 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.11.5 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.12 Unexpected continuation bytes
Case 6.12.1 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.12.2 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.12.3 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.12.4 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.12.5 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.12.6 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.12.7 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.12.8 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.13 Lonely start characters
Case 6.13.1 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.13.2 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.13.3 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.13.4 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.13.5 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.14 Sequences with last continuation byte missing
Case 6.14.1 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.14.2 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.14.3 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.14.4 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.14.5 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.14.6 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.14.7 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.14.8 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.14.9 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.14.10 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.15 Concatenation of incomplete sequences
Case 6.15.1 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.16 Impossible bytes
Case 6.16.1 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.16.2 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.16.3 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.17 Examples of an overlong ASCII character
Case 6.17.1 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.17.2 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.17.3 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.17.4 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.17.5 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.18 Maximum overlong sequences
Case 6.18.1 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.18.2 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.18.3 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.18.4 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.18.5 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.19 Overlong representation of the NUL character
Case 6.19.1 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.19.2 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.19.3 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.19.4 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.19.5 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.20 Single UTF-16 surrogates
Case 6.20.1 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.20.2 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.20.3 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.20.4 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.20.5 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.20.6 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.20.7 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.21 Paired UTF-16 surrogates
Case 6.21.1 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.21.2 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.21.3 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.21.4 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.21.5 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.21.6 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.21.7 Pass1007 PassNone PassNone PassNone Pass1007
Case 6.21.8 Pass1007 PassNone PassNone PassNone Pass1007
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.22 Non-character code points (valid UTF-8)
Case 6.22.1 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.2 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.3 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.4 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.5 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.6 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.7 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.8 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.9 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.10 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.11 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.12 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.13 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.14 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.15 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.16 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.17 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.18 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.19 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.20 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.21 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.22 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.23 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.24 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.25 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.26 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.27 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.28 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.29 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.30 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.31 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.32 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.33 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 6.22.34 Pass1000 PassNone Pass1000 PassNone Pass1000
6 UTF-8 Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
6.23 Unicode replacement character
Case 6.23.1 Pass1000 PassNone Pass1000 PassNone Pass1000
7 Close Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
7.1 Basic close behavior (fuzzer initiated)
Case 7.1.1 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 7.1.2 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 7.1.3 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 7.1.4 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 7.1.5 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 7.1.6 Info1000 InfoNone Info1000 InfoNone Info1000
7 Close Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
7.3 Close frame structure: payload length (fuzzer initiated)
Case 7.3.1 Pass1000 PassNone PassNone PassNone Pass1000
Case 7.3.2 Pass1002 PassNone PassNone PassNone Pass1002
Case 7.3.3 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 7.3.4 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 7.3.5 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 7.3.6 Pass1002 PassNone PassNone PassNone Pass1002
7 Close Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
7.5 Close frame structure: payload value (fuzzer initiated)
Case 7.5.1 Pass1007 PassNone PassNone PassNone Pass1007
7 Close Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
7.7 Close frame structure: valid close codes (fuzzer initiated)
Case 7.7.1 Pass1000 PassNone Pass1000 PassNone Pass1000
Case 7.7.2 Pass1000 PassNone Pass1001 PassNone Pass1001
Case 7.7.3 Pass1000 PassNone Pass1002 PassNone Pass1002
Case 7.7.4 Pass1000 PassNone Pass1003 PassNone Pass1003
Case 7.7.5 Pass1000 PassNone Pass1007 PassNone Pass1007
Case 7.7.6 Pass1000 PassNone Pass1008 PassNone Pass1008
Case 7.7.7 Pass1000 PassNone Pass1009 PassNone Pass1009
Case 7.7.8 Pass1000 PassNone Pass1010 PassNone Pass1010
Case 7.7.9 Pass1000 PassNone Pass1011 PassNone Pass1011
Case 7.7.10 Pass1000 PassNone Pass3000 PassNone Pass3000
Case 7.7.11 Pass1000 PassNone Pass3999 PassNone Pass3999
Case 7.7.12 Pass1000 PassNone Pass4000 PassNone Pass4000
Case 7.7.13 Pass1000 PassNone Pass4999 PassNone Pass4999
7 Close Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
7.9 Close frame structure: invalid close codes (fuzzer initiated)
Case 7.9.1 Pass1002 PassNone PassNone PassNone Pass1002
Case 7.9.2 Pass1002 PassNone Fail999 PassNone Pass1002
Case 7.9.3 Pass1002 PassNone Fail1004 PassNone Pass1002
Case 7.9.4 Pass1002 PassNone PassNone PassNone Pass1002
Case 7.9.5 Pass1002 PassNone PassNone PassNone Pass1002
Case 7.9.6 Pass1002 PassNone Fail1012 PassNone Pass1002
Case 7.9.7 Pass1002 PassNone Fail1013 PassNone Pass1002
Case 7.9.8 Pass1002 PassNone Fail1014 PassNone Pass1002
Case 7.9.9 Pass1002 PassNone PassNone PassNone Pass1002
Case 7.9.10 Pass1002 PassNone Fail1016 PassNone Pass1002
Case 7.9.11 Pass1002 PassNone Fail1100 PassNone Pass1002
Case 7.9.12 Pass1002 PassNone Fail2000 PassNone Pass1002
Case 7.9.13 Pass1002 PassNone Fail2999 PassNone Pass1002
7 Close Handling AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
7.13 Informational close information (fuzzer initiated)
Case 7.13.1 Info1002 InfoNone Info5000 InfoNone Info1002
Case 7.13.2 Info1002 InfoNone Info65535 InfoNone Info1002
9 Limits/Performance AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
9.1 Text Message (increasing size)
Case 9.1.1 Pass
130 ms
1000 Pass
74 ms
None Pass
69 ms
1000 Pass
80 ms
None Pass
69 ms
1000
Case 9.1.2 Pass
508 ms
1000 Pass
295 ms
None Pass
274 ms
1000 Pass
270 ms
None Pass
277 ms
1000
Case 9.1.3 Pass
2032 ms
1000 Pass
1171 ms
None Pass
1032 ms
1000 Pass
1108 ms
None Pass
1093 ms
1000
Case 9.1.4 Pass
8331 ms
1000 Pass
5607 ms
None Pass
4172 ms
1000 Pass
5381 ms
None Pass
4378 ms
1000
Case 9.1.5 Pass
16427 ms
1000 Pass
13961 ms
None Pass
8322 ms
1000 Pass
16139 ms
None Pass
8740 ms
1000
Case 9.1.6 Pass
32866 ms
1000 Pass
37077 ms
None Pass
16576 ms
1000 Pass
51047 ms
None Pass
17787 ms
1000
9 Limits/Performance AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
9.2 Binary Message (increasing size)
Case 9.2.1 Pass
49 ms
1000 Pass
26 ms
None Pass
27 ms
1000 Pass
29 ms
None Pass
29 ms
1000
Case 9.2.2 Pass
186 ms
1000 Pass
105 ms
None Pass
105 ms
1000 Pass
108 ms
None Pass
107 ms
1000
Case 9.2.3 Pass
746 ms
1000 Pass
479 ms
None Pass
396 ms
1000 Pass
452 ms
None Pass
453 ms
1000
Case 9.2.4 Pass
2981 ms
1000 Pass
2849 ms
None Pass
1541 ms
1000 Pass
2740 ms
None Pass
1687 ms
1000
Case 9.2.5 Pass
5970 ms
1000 Pass
7942 ms
None Pass
3161 ms
1000 Pass
10135 ms
None Pass
3398 ms
1000
Case 9.2.6 Pass
11989 ms
1000 Pass
25343 ms
None Pass
6337 ms
1000 Pass
38856 ms
None Pass
6766 ms
1000
9 Limits/Performance AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
9.3 Fragmented Text Message (fixed size, increasing fragment size)
Case 9.3.1 Pass
10407 ms
1000 Pass
4958 ms
None Pass
4874 ms
1000 Pass
4991 ms
None Pass
5136 ms
1000
Case 9.3.2 Pass
8784 ms
1000 Pass
4393 ms
None Pass
4411 ms
1000 Pass
4441 ms
None Pass
4493 ms
1000
Case 9.3.3 Pass
8285 ms
1000 Pass
4233 ms
None Pass
4200 ms
1000 Pass
4293 ms
None Pass
4330 ms
1000
Case 9.3.4 Pass
8117 ms
1000 Pass
4172 ms
None Pass
4069 ms
1000 Pass
4233 ms
None Pass
4368 ms
1000
Case 9.3.5 Pass
8129 ms
1000 Pass
4175 ms
None Pass
4052 ms
1000 Pass
4358 ms
None Pass
4355 ms
1000
Case 9.3.6 Pass
8128 ms
1000 Pass
4141 ms
None Pass
4062 ms
1000 Pass
4189 ms
None Pass
4538 ms
1000
Case 9.3.7 Pass
8114 ms
1000 Pass
4182 ms
None Pass
4080 ms
1000 Pass
4254 ms
None Pass
4434 ms
1000
Case 9.3.8 Pass
8117 ms
1000 Pass
4417 ms
None Pass
4069 ms
1000 Pass
4419 ms
None Pass
4290 ms
1000
Case 9.3.9 Pass
8072 ms
1000 Pass
5428 ms
None Pass
4084 ms
1000 Pass
5150 ms
None Pass
4300 ms
1000
9 Limits/Performance AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
9.4 Fragmented Binary Message (fixed size, increasing fragment size)
Case 9.4.1 Pass
4938 ms
1000 Pass
2287 ms
None Pass
2256 ms
1000 Pass
2336 ms
None Pass
2385 ms
1000
Case 9.4.2 Pass
3461 ms
1000 Pass
1730 ms
None Pass
1707 ms
1000 Pass
1744 ms
None Pass
1835 ms
1000
Case 9.4.3 Pass
3049 ms
1000 Pass
1566 ms
None Pass
1536 ms
1000 Pass
1596 ms
None Pass
1619 ms
1000
Case 9.4.4 Pass
2951 ms
1000 Pass
1536 ms
None Pass
1497 ms
1000 Pass
1579 ms
None Pass
1590 ms
1000
Case 9.4.5 Pass
2915 ms
1000 Pass
1551 ms
None Pass
1491 ms
1000 Pass
1567 ms
None Pass
1560 ms
1000
Case 9.4.6 Pass
2891 ms
1000 Pass
1535 ms
None Pass
1475 ms
1000 Pass
1584 ms
None Pass
1527 ms
1000
Case 9.4.7 Pass
2889 ms
1000 Pass
1539 ms
None Pass
1520 ms
1000 Pass
1642 ms
None Pass
1511 ms
1000
Case 9.4.8 Pass
2923 ms
1000 Pass
1747 ms
None Pass
1492 ms
1000 Pass
1770 ms
None Pass
1523 ms
1000
Case 9.4.9 Pass
2894 ms
1000 Pass
2711 ms
None Pass
1469 ms
1000 Pass
2348 ms
None Pass
1533 ms
1000
9 Limits/Performance AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
9.5 Text Message (fixed size, increasing chop size)
Case 9.5.1 Pass
2896 ms
1000 Pass
2891 ms
None Pass
2638 ms
1000 Pass
2568 ms
None Pass
2552 ms
1000
Case 9.5.2 Pass
2139 ms
1000 Pass
1904 ms
None Pass
1797 ms
1000 Pass
1874 ms
None Pass
1795 ms
1000
Case 9.5.3 Pass
2087 ms
1000 Pass
1512 ms
None Pass
1431 ms
1000 Pass
1437 ms
None Pass
1417 ms
1000
Case 9.5.4 Pass
2050 ms
1000 Pass
1330 ms
None Pass
1305 ms
1000 Pass
1259 ms
None Pass
1255 ms
1000
Case 9.5.5 Pass
2048 ms
1000 Pass
1233 ms
None Pass
1163 ms
1000 Pass
1145 ms
None Pass
1175 ms
1000
Case 9.5.6 Pass
2049 ms
1000 Pass
1184 ms
None Pass
1110 ms
1000 Pass
1118 ms
None Pass
1083 ms
1000
9 Limits/Performance AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
9.6 Binary Text Message (fixed size, increasing chop size)
Case 9.6.1 Pass
2227 ms
1000 Pass
2091 ms
None Pass
1923 ms
1000 Pass
1972 ms
None Pass
1904 ms
1000
Case 9.6.2 Pass
1488 ms
1000 Pass
1269 ms
None Pass
1157 ms
1000 Pass
1190 ms
None Pass
1196 ms
1000
Case 9.6.3 Pass
1124 ms
1000 Pass
916 ms
None Pass
770 ms
1000 Pass
774 ms
None Pass
790 ms
1000
Case 9.6.4 Pass
925 ms
1000 Pass
661 ms
None Pass
580 ms
1000 Pass
592 ms
None Pass
570 ms
1000
Case 9.6.5 Pass
836 ms
1000 Pass
575 ms
None Pass
479 ms
1000 Pass
500 ms
None Pass
474 ms
1000
Case 9.6.6 Pass
786 ms
1000 Pass
524 ms
None Pass
434 ms
1000 Pass
457 ms
None Pass
429 ms
1000
9 Limits/Performance AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
9.7 Text Message Roundtrip Time (fixed number, increasing size)
Case 9.7.1 Pass
285 ms
1000 Pass
282 ms
None Pass
287 ms
1000 Pass
244 ms
None Pass
181 ms
1000
Case 9.7.2 Pass
365 ms
1000 Pass
339 ms
None Pass
302 ms
1000 Pass
257 ms
None Pass
224 ms
1000
Case 9.7.3 Pass
523 ms
1000 Pass
407 ms
None Pass
477 ms
1000 Pass
342 ms
None Pass
305 ms
1000
Case 9.7.4 Pass
1054 ms
1000 Pass
727 ms
None Pass
731 ms
1000 Pass
614 ms
None Pass
559 ms
1000
Case 9.7.5 Pass
2745 ms
1000 Pass
1896 ms
None Pass
1706 ms
1000 Pass
1694 ms
None Pass
1694 ms
1000
Case 9.7.6 Pass
8881 ms
1000 Pass
5207 ms
None Pass
4868 ms
1000 Pass
5000 ms
None Pass
4957 ms
1000
9 Limits/Performance AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
9.8 Binary Message Roundtrip Time (fixed number, increasing size)
Case 9.8.1 Pass
281 ms
1000 Pass
286 ms
None Pass
326 ms
1000 Pass
223 ms
None Pass
183 ms
1000
Case 9.8.2 Pass
329 ms
1000 Pass
314 ms
None Pass
417 ms
1000 Pass
237 ms
None Pass
207 ms
1000
Case 9.8.3 Pass
404 ms
1000 Pass
357 ms
None Pass
446 ms
1000 Pass
281 ms
None Pass
252 ms
1000
Case 9.8.4 Pass
605 ms
1000 Pass
501 ms
None Pass
560 ms
1000 Pass
388 ms
None Pass
360 ms
1000
Case 9.8.5 Pass
1356 ms
1000 Pass
1056 ms
None Pass
1006 ms
1000 Pass
909 ms
None Pass
838 ms
1000
Case 9.8.6 Pass
3796 ms
1000 Pass
2625 ms
None Pass
2343 ms
1000 Pass
2440 ms
None Pass
2374 ms
1000
10 Misc AutobahnClient/0.5.8 Chrome/22.0.1229.94 Firefox/16.0-20100101 Safari/536.26.14 WebSocket /0.2.0-dev
10.1 Auto-Fragmentation
Case 10.1.1 Pass1000 PassNone Pass1000 PassNone 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:
Îºá½¹ÏƒÎ¼Îµí €edited
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:
Îºá½¹ÏƒÎ¼Îµí €edited
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 0x11000 encoded as in the UTF-8 integer encoding scheme, but the codepoint is invalid (out of range).

MESSAGE PARTS:
PART1 = κόσμε (cebae1bdb9cf83cebcceb5)
PART2 = ô€€ (f4908080)
PART3 = edited (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 = €€edited (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 = edited (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.

MESSAGE:
κόσμε
cebae1bdb9cf83cebcceb5

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.

MESSAGE:
Î
ce

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.

MESSAGE:
κ
ceba

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.

MESSAGE:
뼇
cebae1

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.

MESSAGE:
κá½
cebae1bd

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.

MESSAGE:
κό
cebae1bdb9

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.

MESSAGE:
κόÏ
cebae1bdb9cf

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.

MESSAGE:
κόσ
cebae1bdb9cf83

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.

MESSAGE:
κόσÎ
cebae1bdb9cf83ce

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.

MESSAGE:
κόσμ
cebae1bdb9cf83cebc

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.

MESSAGE:
κόσμÎ
cebae1bdb9cf83cebcce

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.

MESSAGE:
κόσμε
cebae1bdb9cf83cebcceb5

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.

MESSAGE:

00

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.

MESSAGE:
€
c280

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.

MESSAGE:
à €
e0a080

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.

MESSAGE:
ð€€
f0908080

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.

MESSAGE:
øˆ€€€
f888808080

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.

MESSAGE:
ü„€€€€
fc8480808080

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.

MESSAGE:

7f

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.

MESSAGE:
ß¿
dfbf

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.

MESSAGE:
ï¿¿
efbfbf

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.

MESSAGE:
ô¿¿
f48fbfbf

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.

MESSAGE:
÷¿¿¿
f7bfbfbf

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.

MESSAGE:
û¿¿¿¿
fbbfbfbfbf

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.

MESSAGE:
ý¿¿¿¿¿
fdbfbfbfbfbf

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.

MESSAGE:
퟿
ed9fbf

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.

MESSAGE:

ee8080

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.

MESSAGE:
�
efbfbd

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.

MESSAGE:
ô¿¿
f48fbfbf

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.

MESSAGE:
ô€€
f4908080

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.

MESSAGE:

80

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.

MESSAGE:
¿
bf

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.

MESSAGE:
€¿
80bf

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.

MESSAGE:
€¿€
80bf80

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.

MESSAGE:
€¿€¿
80bf80bf

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.

MESSAGE:
€¿€¿€
80bf80bf80

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.

MESSAGE:
€¿€¿€¿
80bf80bf80bf

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.

MESSAGE:
€‚ƒ„…†‡ˆ‰Š‹ŒŽ‘’“”•–—˜™š›œžŸ ¡¢£¤¥¦§¨©ª«¬­®¯°±²³´µ¶·¸¹º»¼½¾
808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9fa0a1a2a3a4a5a6a7a8a9aaabacadaeafb0b1b2b3b4b5b6b7b8b9babbbcbdbe

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.

MESSAGE:
À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï Ð Ñ Ò Ó Ô Õ Ö × Ø Ù Ú Û Ü Ý Þ
c020c120c220c320c420c520c620c720c820c920ca20cb20cc20cd20ce20cf20d020d120d220d320d420d520d620d720d820d920da20db20dc20dd20de20

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.

MESSAGE:
à á â ã ä å æ ç è é ê ë ì í î
e020e120e220e320e420e520e620e720e820e920ea20eb20ec20ed20ee20

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.

MESSAGE:
ð ñ ò ó ô õ ö
f020f120f220f320f420f520f620

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.

MESSAGE:
ø ù ú
f820f920fa20

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.

MESSAGE:
ü
fc20

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.

MESSAGE:
À
c0

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.

MESSAGE:
à€
e080

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.

MESSAGE:
ð€€
f08080

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.

MESSAGE:
ø€€€
f8808080

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.

MESSAGE:
ü€€€€
fc80808080

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.

MESSAGE:
ß
df

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.

MESSAGE:
ï¿
efbf

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.

MESSAGE:
÷¿¿
f7bfbf

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.

MESSAGE:
û¿¿¿
fbbfbfbf

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.

MESSAGE:
ý¿¿¿¿
fdbfbfbfbf

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.

MESSAGE:
Àà€ð€€ø€€€ü€€€€ßï¿÷¿¿û¿¿¿ý¿¿¿¿
c0e080f08080f8808080fc80808080dfefbff7bfbffbbfbfbffdbfbfbfbf

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.

MESSAGE:
þ
fe

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.

MESSAGE:
ÿ
ff

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.

MESSAGE:
þþÿÿ
fefeffff

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.

MESSAGE:
À¯
c0af

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.

MESSAGE:
à€¯
e080af

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.

MESSAGE:
ð€€¯
f08080af

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.

MESSAGE:
ø€€€¯
f8808080af

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.

MESSAGE:
ü€€€€¯
fc80808080af

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.

MESSAGE:
Á¿
c1bf

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.

MESSAGE:
àŸ¿
e09fbf

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.

MESSAGE:
ð¿¿
f08fbfbf

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.

MESSAGE:
ø‡¿¿¿
f887bfbfbf

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.

MESSAGE:
üƒ¿¿¿¿
fc83bfbfbfbf

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.

MESSAGE:
À€
c080

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.

MESSAGE:
à€€
e08080

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.

MESSAGE:
ð€€€
f0808080

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.

MESSAGE:
ø€€€€
f880808080

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.

MESSAGE:
ü€€€€€
fc8080808080

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.

MESSAGE:
í €
eda080

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.

MESSAGE:
í­¿
edadbf

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.

MESSAGE:
í®€
edae80

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.

MESSAGE:
í¯¿
edafbf

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.

MESSAGE:
í°€
edb080

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.

MESSAGE:
í¾€
edbe80

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.

MESSAGE:
í¿¿
edbfbf

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.

MESSAGE:
𐀀
eda080edb080

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.

MESSAGE:
𐏿
eda080edbfbf

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.

MESSAGE:
í­¿í°€
edadbfedb080

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.

MESSAGE:
í­¿í¿¿
edadbfedbfbf

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.

MESSAGE:
󰀀
edae80edb080

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.

MESSAGE:
󰏿
edae80edbfbf

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.

MESSAGE:
􏰀
edafbfedb080

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.

MESSAGE:
􏿿
edafbfedbfbf

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.

MESSAGE:
￾
efbfbe

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.

MESSAGE:
ï¿¿
efbfbf

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.

MESSAGE:
🿾
f09fbfbe

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.

MESSAGE:
🿿
f09fbfbf

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.

MESSAGE:
𯿾
f0afbfbe

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.

MESSAGE:
𯿿
f0afbfbf

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.

MESSAGE:
ð¿¿¾
f0bfbfbe

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.

MESSAGE:
ð¿¿¿
f0bfbfbf

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.

MESSAGE:
ñ¿¾
f18fbfbe

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.

MESSAGE:
ñ¿¿
f18fbfbf

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.

MESSAGE:
񟿾
f19fbfbe

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.

MESSAGE:
񟿿
f19fbfbf

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.

MESSAGE:
񯿾
f1afbfbe

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.

MESSAGE:
񯿿
f1afbfbf

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.

MESSAGE:
ñ¿¿¾
f1bfbfbe

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.

MESSAGE:
ñ¿¿¿
f1bfbfbf

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.

MESSAGE:
ò¿¾
f28fbfbe

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.

MESSAGE:
ò¿¿
f28fbfbf

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.

MESSAGE:
򟿾
f29fbfbe

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.

MESSAGE:
òŸ¿¿
f29fbfbf

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.

MESSAGE:
򯿾
f2afbfbe

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.

MESSAGE:
򯿿
f2afbfbf

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.

MESSAGE:
ò¿¿¾
f2bfbfbe

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.

MESSAGE:
ò¿¿¿
f2bfbfbf

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.

MESSAGE:
ó¿¾
f38fbfbe

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.

MESSAGE:
ó¿¿
f38fbfbf

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.

MESSAGE:
󟿾
f39fbfbe

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.

MESSAGE:
óŸ¿¿
f39fbfbf

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.

MESSAGE:
󯿾
f3afbfbe

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.

MESSAGE:
󯿿
f3afbfbf

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.

MESSAGE:
ó¿¿¾
f3bfbfbe

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.

MESSAGE:
ó¿¿¿
f3bfbfbf

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.

MESSAGE:
ô¿¾
f48fbfbe

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.

MESSAGE:
ô¿¿
f48fbfbf

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.

MESSAGE:
�
efbfbd

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.