wsgo fuzzing client - Case 6.4.2 : Fail - 1001 ms @ 2025-03-31T15:47:16.779Z
Case Description
Same as Case 6.4.1, but in 2nd frame, we send only up to and including the octet making the complete payload invalid.
MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5f4
PART2 = 90
PART3 = 8080656469746564
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 differ from any expected.
Expected:
{'OK': [('timeout', 'A')], 'NON-STRICT': [('timeout', 'A'), ('timeout', 'B')]}
Observed:
[]
Case Closing Behavior
The connection was failed by the wrong endpoint (FAILED)
GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: localhost:8080 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: KG44j19pNI0qM3hojwR1SA== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: Upgrade Sec-Websocket-Accept: bAUlA2scM4l0P2U7z1JD12Q7lXw= Upgrade: websocket
| 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 | peer did not respond (in time) in closing handshake | 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 | True | 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 | UTF-8 text message payload ended within Unicode code point 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 |
| 14 | 1 | 14 |
| 129 | 1 | 129 |
| Total | 2 | 143 |
| Chop Size | Count | Octets |
| 18 | 1 | 18 |
| 92 | 1 | 92 |
| 240 | 1 | 240 |
| Total | 3 | 350 |
| Opcode | Count |
| 1 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 1 |
| 8 | 1 |
| Total | 2 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
322d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772
6164650d0a5365632d576562736f ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=12, MASK=bbcb608d, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0xcebae1bdb9cf83cebcceb5f4
003 TX OCTETS: 018cbbcb608d757181300204e3430705d579
004 DELAY 1.000000 sec for TAG A
005 RX OCTETS: 810ccebae1bdb9cf83cebcceb5f4
006 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=12, MASKED=False, MASK=None
0xcebae1bdb9cf83cebcceb5f4
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=86, MASK=3996b7ba, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03ef5554462d382074657874206d657373616765207061796c6f616420656e6465642077697468696e20556e69636f6465
20636f646520706f696e7420617420 ...
008 TX OCTETS: 88d63996b7ba3a79e2ee7fbb8f9a4df3cfce19fbd2c94af7d0df19e6d6c355f9d6de19f3d9de5cf297cd50e2dfd357b6e2d4
50f5d8de5cb6d4d55df397ca56ff ...
009 DELAY TIMEOUT on TAG A
010 TCP DROPPED BY ME