wsgo fuzzing client - Case 6.4.4 : Fail - 2002 ms @ 2025-03-31T15:47:19.795Z

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:
{'OK': [('timeout', 'A')], 'NON-STRICT': [('timeout', 'A'), ('timeout', 'B')]}

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

               322d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772

               6164650d0a5365632d576562736f ...

002 TX OCTETS: 019590281dc8

003 TX OCTETS: 5e92fc7529e79e062ce6a83c

004 DELAY 1.000000 sec for TAG A

005 DELAY TIMEOUT on TAG A

006 TX OCTETS: 00

007 DELAY 1.000000 sec for TAG B

008 DELAY TIMEOUT on TAG B

009 TX OCTETS: a89dadf44169adf4

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

011 TX OCTETS: 8080d852bcc7

012 FAIL CONNECTION AFTER 1.000000 sec

013 RX OCTETS: 8115cebae1bdb9cf83cebcceb5f4908080656469746564

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

               0x03ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e672074657874

               206d65737361676520617420706179 ...

015 TX OCTETS: 88d3c16cb227c283d749a203c749b509c042a54cdb49b70dde4ea54ce77387418a07b604db4ba44cc255ae0fd754b205dc40

               e118d75fb54cdf42b21fd340a44c ...

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

017 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
23	1	23
129	1	129
Total	2	152