Case Description

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

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

Case Expectation

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

Case Outcome

Actual events match at least one expected.

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

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

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 RX OCTETS: 474554202f72756e436173653f636173653d3736266167656e743d7961776c20485454502f312e310d0a436f6e6e65637469

               6f6e3a206b6565702d616c697665 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e372e ...

002 TX OCTETS: 0115

003 TX OCTETS: cebae1bdb9cf83cebcceb5

004 DELAY 1.000000 sec for TAG A

005 RX OCTETS: 018b4345d0cf

006 RX OCTETS: 8dff3172fa8a5301ff8b65

007 RX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=11, MASKED=True, MASK=3433343564306366

               κόσμε

008 DELAY TIMEOUT on TAG A

009 TX OCTETS: f4908080

010 DELAY 1.000000 sec for TAG B

011 RX OCTETS: 0084aa2e4b955ebecb15

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

               0x03ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e672074657874

               206d65737361676520617420706179 ...

013 TX OCTETS: 885303ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e6720746578

               74206d6573736167652061742070 ...

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

015 RX OCTETS: 0086494b8a54

016 RX OCTETS: c11889bb2c2588964d16e0a14efc89cf3b778cc8293692c43e7392d7283682c83965

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

018 TCP DROPPED BY ME

Key	Value	Description
isServer	True	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 WebSockets 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
6	2	12
10	1	10
11	1	11
34	1	34
234	1	234
Total	6	301

Chop Size	Count	Octets
2	1	2
4	1	4
11	1	11
85	1	85
170	1	170
Total	5	272

Opcode	Count
0	2
1	1
Total	3

Opcode	Count
8	1
Total	1