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 Outcome

Actual events match at least one expected.

Expected:
{'NON-STRICT': [('timeout', 'A'), ('timeout', 'B')], 'OK': [('timeout', 'A')]}

Observed:
[('timeout', 'A'), ('timeout', 'B')]

Case Closing Behavior

The connection was failed by the wrong endpoint (FAILED)

Opening Handshake

Closing Behavior

Wire Statistics

Octets Received by Chop Size

Octets Transmitted by Chop Size

Frames Received by Opcode

Frames Transmitted by Opcode

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e

               362d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e31203130312057656220536f636b65742050726f746f636f6c2048616e647368616b650d0a536572766572

               3a20676f2f6563686f7365727665 ...

002 TX OCTETS: 0195d350c117

003 TX OCTETS: 1dea20aa6a9f42d96f9e74e3

004 DELAY 1.000000 sec for TAG A

005 DELAY TIMEOUT on TAG A

006 TX OCTETS: 43

007 DELAY 1.000000 sec for TAG B

008 DELAY TIMEOUT on TAG B

009 TX OCTETS: d04172b739b572b7

010 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=7ee7ea85, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

011 TX OCTETS: 80807ee7ea85

012 FAIL CONNECTION AFTER 1.000000 sec

013 RX OCTETS: 0115cebae1bdb9cf83cebcceb5f49080806564697465648000

014 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=83, MASK=10052ac8, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e672074657874

               206d65737361676520617420706179 ...

015 TX OCTETS: 88d310052ac813ea4fa6736a5fa6646058ad742543a6666446a174257f9c562812e8676d43a475255aba7f664fbb636c44af

               30714fb0642547ad63764baf7525 ...

016 RX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None

017 RX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None

018 TCP DROPPED BY ME

Key	Value	Description
isServer	False	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	True	True, iff I have initiated closing handshake (that is, did send close first).
failedByMe	True	True, iff I have failed the WS connection (i.e. due to protocol error). Failing can be either by initiating closing handshake or brutal drop TCP.
droppedByMe	True	True, iff I dropped the TCP connection.
wasClean	False	True, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReason	None	When wasClean == False, the reason what happened.
wasServerConnectionDropTimeout	False	When we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeout	False	When performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeout	False	When we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode	1007	The close code I sent in close frame (if any).
localCloseReason	encountered invalid UTF-8 while processing text message at payload octet index 12	The close reason I sent in close frame (if any).
remoteCloseCode	None	The close code the peer sent me in close frame (if any).
remoteCloseReason	None	The close reason the peer sent me in close frame (if any).

Chop Size	Count	Octets
25	1	25
162	1	162
Total	2	187