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 Outcome

Actual events match at least one expected.

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

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

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: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374

               53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393039300d0a557067726164653a20776562736f

               636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a2044555970

               457a4f37364f6638544755366469667274673d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d

0a

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b

               65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a206c5448

               58445436726d32666668625a577255594335757264564c513d0d0a0d0a

002 TX FRAME : OPCODE=1, FIN=False, RSV=0, MASK=e03629fd, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               κόσμε

003 TX OCTETS: 018be03629fd2e8cc84059f9aa335cf89c

004 DELAY 1.000000 sec for TAG A

005 DELAY TIMEOUT on TAG A

006 TX FRAME : OPCODE=0, FIN=False, RSV=0, MASK=6accb181, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               ����

007 TX OCTETS: 00846accb1819e5c3101

008 DELAY 1.000000 sec for TAG B

009 RX OCTETS: 880203ef

010 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None

�

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

�

012 TX OCTETS: 88821af58ac2191d

013 TCP DROPPED BY PEER

Key	Value	Description
isServer	False	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	False	True, iff I have initiated closing handshake (that is, did send close first).
failedByMe	False	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	False	True, iff I dropped the TCP connection.
wasClean	True	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.
wasCloseHandshakeTimeout	False	When we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode	1000	The close code I sent in close frame (if any).
localCloseReason	None	The close reason I sent in close frame (if any).
remoteCloseCode	1007	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
4	1	4
129	1	129
Total	2	133