GoWebSock - Case 7.5.1 : Pass - 1 ms @ 2025-04-20T09:27:40.686Z
Case Description
Send a close frame with invalid UTF8 payload
Case Expectation
Clean close with protocol error or invalid utf8 code or dropped TCP.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /echo HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: host.docker.internal:8080 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: zwaB9gAI/I4//H+0M5Ed/Q== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: Upgrade Sec-WebSocket-Accept: iQN4nFRpGSvhI3eckXvReobOsyQ= Sec-WebSocket-Version: 13 Server: GoWebSock 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 | 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 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 | 1000 | The close code I sent in close frame (if any). |
| localCloseReason | cebae1bdb9cf83cebcceb5eda080656469746564 | 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 | protocol error: invalid UTF-8 in close reason | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 49 | 1 | 49 |
| 175 | 1 | 175 |
| Total | 2 | 224 |
| Chop Size | Count | Octets |
| 28 | 1 | 28 |
| 255 | 1 | 255 |
| Total | 2 | 283 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
000 TX OCTETS: 474554202f6563686f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f
302e382e322d302e31302e390d0a ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772
6164650d0a5365632d576562536f ...
002 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=22, MASK=878d5adf, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8cebae1bdb9cf83cebcceb5eda080656469746564
003 TX OCTETS: 8896878d5adf846594656630e3100443e6113260fa5fe2e933abe2e9
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 882f03ef70726f746f636f6c206572726f723a20696e76616c6964205554462d3820696e20636c6f736520726561736f6e
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=47, MASKED=False, MASK=None
0x03ef70726f746f636f6c206572726f723a20696e76616c6964205554462d3820696e20636c6f736520726561736f6e
007 TCP DROPPED BY PEER