WebSockets Protocol Test Report

Test summary report generated on

2011-09-22T18:47:40Z

by Autobahn WebSockets.

Test Results

1 FramingAutobahnServer/0.4.2WebSocket++ snapshot
1.1 Text Messages
Case 1.1.1Pass1000Pass1000
Case 1.1.2Pass1000Pass1000
Case 1.1.3Pass1000Pass1000
Case 1.1.4Pass1000Pass1000
Case 1.1.5Pass1000Pass1000
Case 1.1.6Pass1000Pass1000
Case 1.1.7Pass1000Pass1000
Case 1.1.8Pass1000Pass1000
1.2 Binary Messages
Case 1.2.1Pass1000Pass1000
Case 1.2.2Pass1000Pass1000
Case 1.2.3Pass1000Pass1000
Case 1.2.4Pass1000Pass1000
Case 1.2.5Pass1000Pass1000
Case 1.2.6Pass1000Pass1000
Case 1.2.7Pass1000Pass1000
Case 1.2.8Pass1000Pass1000
2 Pings/PongsAutobahnServer/0.4.2WebSocket++ snapshot
Case 2.1Pass1000Pass1000
Case 2.2Pass1000Pass1000
Case 2.3Pass1000Pass1000
Case 2.4Pass1000Pass1000
Case 2.5PassNonePassFail
Case 2.6Pass1000Pass1000
Case 2.7Pass1000Pass1000
Case 2.8Pass1000Pass1000
Case 2.9Pass1000Pass1000
Case 2.10Pass1000Pass1000
Case 2.11Pass1000Pass1000
3 Reserved BitsAutobahnServer/0.4.2WebSocket++ snapshot
Case 3.1PassNonePassFail
Case 3.2PassNonePassFail
Case 3.3PassNonePassFail
Case 3.4PassNonePassFail
Case 3.5PassNonePassFail
Case 3.6PassNonePassFail
Case 3.7PassNonePassFail
4 OpcodesAutobahnServer/0.4.2WebSocket++ snapshot
4.1 Non-control Opcodes
Case 4.1.1PassNonePassFail
Case 4.1.2PassNonePassFail
Case 4.1.3PassNonePassFail
Case 4.1.4PassNonePassFail
Case 4.1.5PassNonePassFail
4.2 Control Opcodes
Case 4.2.1PassNonePassFail
Case 4.2.2PassNonePassFail
Case 4.2.3PassNonePassFail
Case 4.2.4PassNonePassFail
Case 4.2.5PassNonePassFail
5 FragmentationAutobahnServer/0.4.2WebSocket++ snapshot
Case 5.1PassNonePassFail
Case 5.2PassNonePassFail
Case 5.3Pass1000Pass1000
Case 5.4Pass1000Pass1000
Case 5.5Pass1000Pass1000
Case 5.6Pass1000Pass1000
Case 5.7Pass1000Pass1000
Case 5.8Pass1000Pass1000
Case 5.9PassNonePassFail
Case 5.10PassNonePassFail
Case 5.11PassNonePassFail
Case 5.12PassNonePassFail
Case 5.13PassNonePassFail
Case 5.14PassNonePassFail
Case 5.15PassNonePassFail
Case 5.16PassNonePassFail
Case 5.17PassNonePassFail
Case 5.18PassNonePassFail
Case 5.19Pass1000Pass1000
Case 5.20Pass1000Pass1000
6 UTF-8 HandlingAutobahnServer/0.4.2WebSocket++ snapshot
6.1 Valid UTF-8 with zero payload fragments
Case 6.1.1Pass1000Pass1000
Case 6.1.2Pass1000Pass1000
Case 6.1.3Pass1000Pass1000
6.2 Valid UTF-8 unfragmented, fragmented on code-points and within code-points
Case 6.2.1Pass1000Pass1000
Case 6.2.2Pass1000Pass1000
Case 6.2.3Pass1000Pass1000
Case 6.2.4Pass1000Pass1000
6.3 Invalid UTF-8 differently fragmented
Case 6.3.1PassNonePassFail
Case 6.3.2PassNonePassFail
6.4 Fail-fast on invalid UTF-8
Case 6.4.1PassNonePassFail
Case 6.4.2PassNonePassFail
Case 6.4.3PassNonePassFail
Case 6.4.4PassNoneNon-StrictFail
Case 6.4.5PassNoneNon-StrictFail
6.5 Some valid UTF-8 sequences
Case 6.5.1Pass1000Pass1000
6.6 All prefixes of a valid UTF-8 string that contains multi-byte code points
Case 6.6.1PassNonePassFail
Case 6.6.2Pass1000Pass1000
Case 6.6.3PassNonePassFail
Case 6.6.4PassNonePassFail
Case 6.6.5Pass1000Pass1000
Case 6.6.6PassNonePassFail
Case 6.6.7Pass1000Pass1000
Case 6.6.8PassNonePassFail
Case 6.6.9Pass1000Pass1000
Case 6.6.10PassNonePassFail
Case 6.6.11Pass1000Pass1000
6.7 First possible sequence of a certain length
Case 6.7.1Pass1000Pass1000
Case 6.7.2Pass1000Pass1000
Case 6.7.3Pass1000Pass1000
Case 6.7.4Pass1000Pass1000
6.8 First possible sequence length 5/6 (invalid codepoints)
Case 6.8.1PassNonePassFail
Case 6.8.2PassNonePassFail
6.9 Last possible sequence of a certain length
Case 6.9.1Pass1000Pass1000
Case 6.9.2Pass1000Pass1000
Case 6.9.3Pass1000Pass1000
Case 6.9.4Pass1000Pass1000
6.10 Last possible sequence length 4/5/6 (invalid codepoints)
Case 6.10.1PassNonePassFail
Case 6.10.2PassNonePassFail
Case 6.10.3PassNonePassFail
6.11 Other boundary conditions
Case 6.11.1Pass1000Pass1000
Case 6.11.2Pass1000Pass1000
Case 6.11.3Pass1000Pass1000
Case 6.11.4Pass1000Pass1000
Case 6.11.5PassNonePassFail
6.12 Unexpected continuation bytes
Case 6.12.1PassNonePassFail
Case 6.12.2PassNonePassFail
Case 6.12.3PassNonePassFail
Case 6.12.4PassNonePassFail
Case 6.12.5PassNonePassFail
Case 6.12.6PassNonePassFail
Case 6.12.7PassNonePassFail
Case 6.12.8PassNonePassFail
6.13 Lonely start characters
Case 6.13.1PassNonePassFail
Case 6.13.2PassNonePassFail
Case 6.13.3PassNonePassFail
Case 6.13.4PassNonePassFail
Case 6.13.5PassNonePassFail
6.14 Sequences with last continuation byte missing
Case 6.14.1PassNonePassFail
Case 6.14.2PassNonePassFail
Case 6.14.3PassNonePassFail
Case 6.14.4PassNonePassFail
Case 6.14.5PassNonePassFail
Case 6.14.6PassNonePassFail
Case 6.14.7PassNonePassFail
Case 6.14.8PassNonePassFail
Case 6.14.9PassNonePassFail
Case 6.14.10PassNonePassFail
6.15 Concatenation of incomplete sequences
Case 6.15.1PassNonePassFail
6.16 Impossible bytes
Case 6.16.1PassNonePassFail
Case 6.16.2PassNonePassFail
Case 6.16.3PassNonePassFail
6.17 Examples of an overlong ASCII character
Case 6.17.1PassNonePassFail
Case 6.17.2PassNonePassFail
Case 6.17.3PassNonePassFail
Case 6.17.4PassNonePassFail
Case 6.17.5PassNonePassFail
6.18 Maximum overlong sequences
Case 6.18.1PassNonePassFail
Case 6.18.2PassNonePassFail
Case 6.18.3PassNonePassFail
Case 6.18.4PassNonePassFail
Case 6.18.5PassNonePassFail
6.19 Overlong representation of the NUL character
Case 6.19.1PassNonePassFail
Case 6.19.2PassNonePassFail
Case 6.19.3PassNonePassFail
Case 6.19.4PassNonePassFail
Case 6.19.5PassNonePassFail
6.20 Single UTF-16 surrogates
Case 6.20.1PassNonePassFail
Case 6.20.2PassNonePassFail
Case 6.20.3PassNonePassFail
Case 6.20.4PassNonePassFail
Case 6.20.5PassNonePassFail
Case 6.20.6PassNonePassFail
Case 6.20.7PassNonePassFail
6.21 Paired UTF-16 surrogates
Case 6.21.1PassNonePassFail
Case 6.21.2PassNonePassFail
Case 6.21.3PassNonePassFail
Case 6.21.4PassNonePassFail
Case 6.21.5PassNonePassFail
Case 6.21.6PassNonePassFail
Case 6.21.7PassNonePassFail
Case 6.21.8PassNonePassFail
6.22 Non-character code points (valid UTF-8)
Case 6.22.1Pass1000Pass1000
Case 6.22.2Pass1000Pass1000
6.23 Unicode replacement character
Case 6.23.1Pass1000Pass1000
7 Close HandlingAutobahnServer/0.4.2WebSocket++ snapshot
Case 7.1Pass1000Pass1000
Case 7.2Pass1000Pass1000
9 Limits/PerformanceAutobahnServer/0.4.2WebSocket++ snapshot
9.1 Text Message (increasing size)
Case 9.1.1MissingMissing
Case 9.1.2MissingMissing
Case 9.1.3MissingMissing
Case 9.1.4MissingMissing
Case 9.1.5MissingMissing
Case 9.1.6MissingMissing
9.2 Binary Message (increasing size)
Case 9.2.1MissingMissing
Case 9.2.2MissingMissing
Case 9.2.3MissingMissing
Case 9.2.4MissingMissing
Case 9.2.5MissingMissing
Case 9.2.6MissingMissing
9.3 Fragmented Text Message (fixed size, increasing fragment size)
Case 9.3.1MissingMissing
Case 9.3.2MissingMissing
Case 9.3.3MissingMissing
Case 9.3.4MissingMissing
Case 9.3.5MissingMissing
Case 9.3.6MissingMissing
Case 9.3.7MissingMissing
Case 9.3.8MissingMissing
Case 9.3.9MissingMissing
9.4 Fragmented Binary Message (fixed size, increasing fragment size)
Case 9.4.1MissingMissing
Case 9.4.2MissingMissing
Case 9.4.3MissingMissing
Case 9.4.4MissingMissing
Case 9.4.5MissingMissing
Case 9.4.6MissingMissing
Case 9.4.7MissingMissing
Case 9.4.8MissingMissing
Case 9.4.9MissingMissing
9.5 Text Message (fixed size, increasing chop size)
Case 9.5.1MissingMissing
Case 9.5.2MissingMissing
Case 9.5.3MissingMissing
Case 9.5.4MissingMissing
Case 9.5.5MissingMissing
Case 9.5.6MissingMissing
9.6 Binary Text Message (fixed size, increasing chop size)
Case 9.6.1MissingMissing
Case 9.6.2MissingMissing
Case 9.6.3MissingMissing
Case 9.6.4MissingMissing
Case 9.6.5MissingMissing
Case 9.6.6MissingMissing

Test Cases

Case 1.1.1

Description

Send text message with payload 0.

Expectation

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

Case 1.1.2

Description

Send text message message with payload of length 125.

Expectation

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

Case 1.1.3

Description

Send text message message with payload of length 126.

Expectation

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

Case 1.1.4

Description

Send text message message with payload of length 127.

Expectation

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

Case 1.1.5

Description

Send text message message with payload of length 128.

Expectation

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

Case 1.1.6

Description

Send text message message with payload of length 65535.

Expectation

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

Case 1.1.7

Description

Send text message message with payload of length 65536.

Expectation

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

Case 1.1.8

Description

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

Expectation

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

Case 1.2.1

Description

Send binary message with payload 0.

Expectation

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

Case 1.2.2

Description

Send binary message message with payload of length 125.

Expectation

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

Case 1.2.3

Description

Send binary message message with payload of length 126.

Expectation

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

Case 1.2.4

Description

Send binary message message with payload of length 127.

Expectation

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

Case 1.2.5

Description

Send binary message message with payload of length 128.

Expectation

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

Case 1.2.6

Description

Send binary message message with payload of length 65535.

Expectation

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

Case 1.2.7

Description

Send binary message message with payload of length 65536.

Expectation

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

Case 1.2.8

Description

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

Expectation

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

Case 2.1

Description

Send ping without payload.

Expectation

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

Case 2.2

Description

Send ping with small text payload.

Expectation

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

Case 2.3

Description

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

Expectation

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

Case 2.4

Description

Send ping with binary payload of 125 octets.

Expectation

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

Case 2.5

Description

Send ping with binary payload of 126 octets.

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

Description

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

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

Description

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

Expectation

Nothing.

Case 2.8

Description

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

Expectation

Nothing.

Case 2.9

Description

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

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

Description

Send 10 Pings with payload.

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

Description

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

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

Description

Send small text message with RSV = 1.

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

Description

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

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

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.

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

Description

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

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

Description

Send small binary message with RSV = 5.

Expectation

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

Case 3.6

Description

Send Ping with RSV = 6.

Expectation

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

Case 3.7

Description

Send Close with RSV = 7.

Expectation

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

Case 4.1.1

Description

Send frame with reserved non-control Opcode = 3.

Expectation

The connection is failed immediately.

Case 4.1.2

Description

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

Expectation

The connection is failed immediately.

Case 4.1.3

Description

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

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

Description

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

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

Description

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

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

Description

Send frame with reserved control Opcode = 11.

Expectation

The connection is failed immediately.

Case 4.2.2

Description

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

Expectation

The connection is failed immediately.

Case 4.2.3

Description

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

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

Description

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

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

Description

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

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

Description

Send Ping fragmented into 2 fragments.

Expectation

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

Case 5.2

Description

Send Pong fragmented into 2 fragments.

Expectation

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

Case 5.3

Description

Send text Message fragmented into 2 fragments.

Expectation

Message is processed and echo'ed back to us.

Case 5.4

Description

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

Expectation

Message is processed and echo'ed back to us.

Case 5.5

Description

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

Expectation

Message is processed and echo'ed back to us.

Case 5.6

Description

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

Expectation

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

Case 5.7

Description

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

Expectation

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

Case 5.8

Description

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

Expectation

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

Case 5.9

Description

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

Expectation

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

Case 5.10

Description

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

Expectation

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

Case 5.11

Description

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

Expectation

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

Case 5.12

Description

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

Expectation

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

Case 5.13

Description

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

Expectation

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

Case 5.14

Description

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

Expectation

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

Case 5.15

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.

Expectation

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

Case 5.16

Description

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

Expectation

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

Case 5.17

Description

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

Expectation

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

Case 5.18

Description

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

Expectation

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

Case 5.19

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.

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

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.

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

Description

Send text message of length 0.

Expectation

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

Case 6.1.2

Description

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

Expectation

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

Case 6.1.3

Description

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

Expectation

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

Case 6.2.1

Description

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

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

Expectation

The message is echo'ed back to us.

Case 6.2.2

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

Expectation

The message is echo'ed back to us.

Case 6.2.3

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

Expectation

The message is echo'ed back to us.

Case 6.2.4

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

Expectation

The message is echo'ed back to us.

Case 6.3.1

Description

Send invalid UTF-8 text message unfragmented.

MESSAGE:
κόσμεedited
cebae1bdb9cf83cebcceb5eda080656469746564

Expectation

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

Case 6.3.2

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

Expectation

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

Case 6.4.1

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 octet making the sequence invalid, then wait, then 3rd frame with rest.

MESSAGE:
κόσμεedited
cebae1bdb9cf83cebcceb5eda080656469746564

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 payload is not valid UTF-8.

Case 6.4.2

Description

Send invalid UTF-8 text message in 3 fragments plus more. First is valid, then wait, then 2nd which contains the octet making the sequence invalid, then wait, then 3rd with rest. Then we send 16 frames each 64k.

MESSAGE:
κόσμεedited
cebae1bdb9cf83cebcceb5eda080656469746564

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 payload is not valid UTF-8.

Case 6.4.3

Description

Send invalid UTF-8 text message in 3 fragments plus more. First is valid, then wait, then 2nd which contains the octet making the sequence invalid, then wait, then 3rd with rest. Then we send 64k frames forever.

MESSAGE:
κόσμεedited
cebae1bdb9cf83cebcceb5eda080656469746564

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 payload is not valid UTF-8.

Case 6.4.4

Description

Send invalid UTF-8 text message in one frame, but 3 chops. First chop is valid, then wait, then send 2nd chop with payload octet making the sequence invalid, then wait, then send test rest of payload in last chop.

MESSAGE:
κόσμεedited
cebae1bdb9cf83cebcceb5eda080656469746564

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) upon receiving the offending octet. If we timeout, we expect the connection is failed at least then, since the payload is not valid UTF-8.

Case 6.4.5

Description

Send invalid UTF-8 text message in 2 fragments plus more. First is valid, then wait, then in 2nd frame, send the octet making the sequence invalid, then wait, then send test rest of 2nd frame. Then we send 64k frames forever.

MESSAGE:
κόσμεedited
cebae1bdb9cf83cebcceb5eda080656469746564

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) upon receiving the offending octet. If we timeout, we expect the connection is failed at least then, since the payload is not valid UTF-8.

Case 6.5.1

Description

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

MESSAGE:
κόσμε
cebae1bdb9cf83cebcceb5

Expectation

The message is echo'ed back to us.

Case 6.6.1

Description

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

MESSAGE:

ce

Expectation

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

Case 6.6.2

Description

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

MESSAGE:
κ
ceba

Expectation

The message is echo'ed back to us.

Case 6.6.3

Description

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

MESSAGE:
κ
cebae1

Expectation

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

Case 6.6.4

Description

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

MESSAGE:
κ
cebae1bd

Expectation

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

Case 6.6.5

Description

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

MESSAGE:
κό
cebae1bdb9

Expectation

The message is echo'ed back to us.

Case 6.6.6

Description

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

MESSAGE:
κό
cebae1bdb9cf

Expectation

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

Case 6.6.7

Description

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

MESSAGE:
κόσ
cebae1bdb9cf83

Expectation

The message is echo'ed back to us.

Case 6.6.8

Description

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

MESSAGE:
κόσ
cebae1bdb9cf83ce

Expectation

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

Case 6.6.9

Description

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

MESSAGE:
κόσμ
cebae1bdb9cf83cebc

Expectation

The message is echo'ed back to us.

Case 6.6.10

Description

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

MESSAGE:
κόσμ
cebae1bdb9cf83cebcce

Expectation

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

Case 6.6.11

Description

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

MESSAGE:
κόσμε
cebae1bdb9cf83cebcceb5

Expectation

The message is echo'ed back to us.

Case 6.7.1

Description

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

MESSAGE:

00

Expectation

The message is echo'ed back to us.

Case 6.7.2

Description

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

MESSAGE:
€
c280

Expectation

The message is echo'ed back to us.

Case 6.7.3

Description

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

MESSAGE:

e0a080

Expectation

The message is echo'ed back to us.

Case 6.7.4

Description

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

MESSAGE:
𐀀
f0908080

Expectation

The message is echo'ed back to us.

Case 6.8.1

Description

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

MESSAGE:

f888808080

Expectation

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

Case 6.8.2

Description

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

MESSAGE:

fc8480808080

Expectation

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

Case 6.9.1

Description

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

MESSAGE:

7f

Expectation

The message is echo'ed back to us.

Case 6.9.2

Description

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

MESSAGE:
߿
dfbf

Expectation

The message is echo'ed back to us.

Case 6.9.3

Description

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

MESSAGE:
￿
efbfbf

Expectation

The message is echo'ed back to us.

Case 6.9.4

Description

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

MESSAGE:
􏿿
f48fbfbf

Expectation

The message is echo'ed back to us.

Case 6.10.1

Description

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

MESSAGE:

f7bfbfbf

Expectation

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

Case 6.10.2

Description

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

MESSAGE:

fbbfbfbfbf

Expectation

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

Case 6.10.3

Description

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

MESSAGE:

fdbfbfbfbfbf

Expectation

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

Case 6.11.1

Description

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

MESSAGE:

ed9fbf

Expectation

The message is echo'ed back to us.

Case 6.11.2

Description

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

MESSAGE:

ee8080

Expectation

The message is echo'ed back to us.

Case 6.11.3

Description

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

MESSAGE:

efbfbd

Expectation

The message is echo'ed back to us.

Case 6.11.4

Description

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

MESSAGE:
􏿿
f48fbfbf

Expectation

The message is echo'ed back to us.

Case 6.11.5

Description

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

MESSAGE:

f4908080

Expectation

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

Case 6.12.1

Description

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

MESSAGE:

80

Expectation

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

Case 6.12.2

Description

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

MESSAGE:

bf

Expectation

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

Case 6.12.3

Description

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

MESSAGE:

80bf

Expectation

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

Case 6.12.4

Description

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

MESSAGE:

80bf80

Expectation

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

Case 6.12.5

Description

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

MESSAGE:

80bf80bf

Expectation

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

Case 6.12.6

Description

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

MESSAGE:

80bf80bf80

Expectation

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

Case 6.12.7

Description

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

MESSAGE:

80bf80bf80bf

Expectation

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

Case 6.12.8

Description

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

MESSAGE:

808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9fa0a1a2a3a4a5a6a7a8a9aaabacadaeafb0b1b2b3b4b5b6b7b8b9babbbcbdbe

Expectation

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

Case 6.13.1

Description

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

MESSAGE:

c020c120c220c320c420c520c620c720c820c920ca20cb20cc20cd20ce20cf20d020d120d220d320d420d520d620d720d820d920da20db20dc20dd20de20

Expectation

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

Case 6.13.2

Description

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

MESSAGE:

e020e120e220e320e420e520e620e720e820e920ea20eb20ec20ed20ee20

Expectation

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

Case 6.13.3

Description

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

MESSAGE:

f020f120f220f320f420f520f620

Expectation

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

Case 6.13.4

Description

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

MESSAGE:

f820f920fa20

Expectation

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

Case 6.13.5

Description

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

MESSAGE:

fc20

Expectation

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

Case 6.14.1

Description

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

MESSAGE:

c0

Expectation

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

Case 6.14.2

Description

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

MESSAGE:

e080

Expectation

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

Case 6.14.3

Description

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

MESSAGE:

f08080

Expectation

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

Case 6.14.4

Description

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

MESSAGE:

f8808080

Expectation

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

Case 6.14.5

Description

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

MESSAGE:

fc80808080

Expectation

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

Case 6.14.6

Description

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

MESSAGE:

df

Expectation

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

Case 6.14.7

Description

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

MESSAGE:

efbf

Expectation

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

Case 6.14.8

Description

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

MESSAGE:

f7bfbf

Expectation

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

Case 6.14.9

Description

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

MESSAGE:

fbbfbfbf

Expectation

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

Case 6.14.10

Description

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

MESSAGE:

fdbfbfbfbf

Expectation

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

Case 6.15.1

Description

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

MESSAGE:

c0e080f08080f8808080fc80808080dfefbff7bfbffbbfbfbffdbfbfbfbf

Expectation

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

Case 6.16.1

Description

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

MESSAGE:

fe

Expectation

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

Case 6.16.2

Description

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

MESSAGE:

ff

Expectation

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

Case 6.16.3

Description

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

MESSAGE:

fefeffff

Expectation

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

Case 6.17.1

Description

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

MESSAGE:

c0af

Expectation

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

Case 6.17.2

Description

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

MESSAGE:

e080af

Expectation

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

Case 6.17.3

Description

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

MESSAGE:

f08080af

Expectation

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

Case 6.17.4

Description

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

MESSAGE:

f8808080af

Expectation

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

Case 6.17.5

Description

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

MESSAGE:

fc80808080af

Expectation

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

Case 6.18.1

Description

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

MESSAGE:

c1bf

Expectation

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

Case 6.18.2

Description

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

MESSAGE:

e09fbf

Expectation

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

Case 6.18.3

Description

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

MESSAGE:

f08fbfbf

Expectation

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

Case 6.18.4

Description

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

MESSAGE:

f887bfbfbf

Expectation

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

Case 6.18.5

Description

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

MESSAGE:

fc83bfbfbfbf

Expectation

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

Case 6.19.1

Description

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

MESSAGE:

c080

Expectation

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

Case 6.19.2

Description

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

MESSAGE:

e08080

Expectation

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

Case 6.19.3

Description

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

MESSAGE:

f0808080

Expectation

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

Case 6.19.4

Description

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

MESSAGE:

f880808080

Expectation

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

Case 6.19.5

Description

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

MESSAGE:

fc8080808080

Expectation

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

Case 6.20.1

Description

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

MESSAGE:

eda080

Expectation

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

Case 6.20.2

Description

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

MESSAGE:

edadbf

Expectation

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

Case 6.20.3

Description

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

MESSAGE:

edae80

Expectation

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

Case 6.20.4

Description

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

MESSAGE:

edafbf

Expectation

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

Case 6.20.5

Description

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

MESSAGE:

edb080

Expectation

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

Case 6.20.6

Description

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

MESSAGE:

edbe80

Expectation

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

Case 6.20.7

Description

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

MESSAGE:

edbfbf

Expectation

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

Case 6.21.1

Description

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

MESSAGE:

eda080edb080

Expectation

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

Case 6.21.2

Description

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

MESSAGE:

eda080edbfbf

Expectation

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

Case 6.21.3

Description

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

MESSAGE:

edadbfedb080

Expectation

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

Case 6.21.4

Description

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

MESSAGE:

edadbfedbfbf

Expectation

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

Case 6.21.5

Description

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

MESSAGE:

edae80edb080

Expectation

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

Case 6.21.6

Description

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

MESSAGE:

edae80edbfbf

Expectation

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

Case 6.21.7

Description

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

MESSAGE:

edafbfedb080

Expectation

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

Case 6.21.8

Description

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

MESSAGE:

edafbfedbfbf

Expectation

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

Case 6.22.1

Description

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

MESSAGE:

efbfbe

Expectation

The message is echo'ed back to us.

Case 6.22.2

Description

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

MESSAGE:
￿
efbfbf

Expectation

The message is echo'ed back to us.

Case 6.23.1

Description

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

MESSAGE:

efbfbd

Expectation

The message is echo'ed back to us.

Case 7.1

Description

Send message after close

Expectation

Receive echo'ed text message. Clean close with normal code.

Case 7.2

Description

Send ping after close

Expectation

Receive echo'ed text message. Clean close with normal code.

Case 9.1.1

Description

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

Expectation

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

Case 9.1.2

Description

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

Expectation

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

Case 9.1.3

Description

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

Expectation

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

Case 9.1.4

Description

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

Expectation

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

Case 9.1.5

Description

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

Expectation

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

Case 9.1.6

Description

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

Expectation

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

Case 9.2.1

Description

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

Expectation

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

Case 9.2.2

Description

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

Expectation

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

Case 9.2.3

Description

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

Expectation

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

Case 9.2.4

Description

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

Expectation

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

Case 9.2.5

Description

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

Expectation

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

Case 9.2.6

Description

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

Expectation

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

Case 9.3.1

Description

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

Expectation

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

Case 9.3.2

Description

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

Expectation

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

Case 9.3.3

Description

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

Expectation

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

Case 9.3.4

Description

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

Expectation

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

Case 9.3.5

Description

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

Expectation

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

Case 9.3.6

Description

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

Expectation

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

Case 9.3.7

Description

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

Expectation

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

Case 9.3.8

Description

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

Expectation

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

Case 9.3.9

Description

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

Expectation

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

Case 9.4.1

Description

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

Expectation

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

Case 9.4.2

Description

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

Expectation

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

Case 9.4.3

Description

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

Expectation

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

Case 9.4.4

Description

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

Expectation

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

Case 9.4.5

Description

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

Expectation

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

Case 9.4.6

Description

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

Expectation

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

Case 9.4.7

Description

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

Expectation

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

Case 9.4.8

Description

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

Expectation

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

Case 9.4.9

Description

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

Expectation

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

Case 9.5.1

Description

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

Expectation

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

Case 9.5.2

Description

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

Expectation

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

Case 9.5.3

Description

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

Expectation

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

Case 9.5.4

Description

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

Expectation

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

Case 9.5.5

Description

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

Expectation

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

Case 9.5.6

Description

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

Expectation

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

Case 9.6.1

Description

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

Expectation

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

Case 9.6.2

Description

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

Expectation

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

Case 9.6.3

Description

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

Expectation

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

Case 9.6.4

Description

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

Expectation

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

Case 9.6.5

Description

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

Expectation

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

Case 9.6.6

Description

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

Expectation

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