wsgo fuzzing client - Case 6.18.1 : Fail - 1 ms @ 2025-03-31T15:47:26.024Z
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xc1bf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
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: a8CUpxhxCryjRbXGq06U7A== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: Upgrade Sec-Websocket-Accept: XcMvKXWTStmn4r+thcoi7tWmV7M= 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 | 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 0 | 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 |
| 4 | 1 | 4 |
| 129 | 1 | 129 |
| Total | 2 | 133 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 88 | 1 | 88 |
| 240 | 1 | 240 |
| Total | 3 | 336 |
| 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=True, RSV=0, PAYLOAD-LEN=2, MASK=88c97134, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0xc1bf
003 TX OCTETS: 818288c971344976
004 FAIL CONNECTION AFTER 0.500000 sec
005 RX OCTETS: 8102c1bf
006 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=82, MASK=7a9ef781, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e672074657874
206d65737361676520617420706179 ...
007 TX OCTETS: 88d27a9ef781797192ef19f182ef0efb85e41ebe9eef0cff9be81ebea2d53cb3cfa10df69eed1fbe87f315fd92f209f799e6
5aea92f90ebe9ae409ed96e61fbe ...
008 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
009 TCP DROPPED BY ME