wsgo fuzzing client - Case 6.6.10 : Fail - 501 ms @ 2025-03-31T15:47:24.346Z
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xcebae1bdb9cf83cebcce
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: kjM1+o57GPPkAVUQutSFXQ== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: Upgrade Sec-Websocket-Accept: sxekeKq8e2ut96PIZsFxj/BTi34= 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 | UTF-8 text message payload ended within Unicode code point at payload octet index 10 | 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 |
| 12 | 1 | 12 |
| 129 | 1 | 129 |
| Total | 2 | 141 |
| Chop Size | Count | Octets |
| 16 | 1 | 16 |
| 92 | 1 | 92 |
| 240 | 1 | 240 |
| Total | 3 | 348 |
| 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=10, MASK=6ba8b4fd, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0xcebae1bdb9cf83cebcce
003 TX OCTETS: 818a6ba8b4fda5125540d2673733d766
004 FAIL CONNECTION AFTER 0.500000 sec
005 RX OCTETS: 810acebae1bdb9cf83cebcce
006 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=10, MASKED=False, MASK=None
0xcebae1bdb9cf83cebcce
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=86, MASK=8aa833ae, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03ef5554462d382074657874206d657373616765207061796c6f616420656e6465642077697468696e20556e69636f6465
20636f646520706f696e7420617420 ...
008 TX OCTETS: 88d68aa833ae894766facc850b8efecd4bdaaac556ddf9c954cbaad852d7e6c752caaacd5dcaefcc13d9e3dc5bc7e48866c0
e3cb5ccaef8850c1eecd13dee5c1 ...
009 FAILING CONNECTION
010 TCP DROPPED BY ME