GoWebSock - Case 4.1.2 : Pass - 1 ms @ 2025-04-20T09:27:29.534Z
Case Description
Send frame with reserved non-control Opcode = 4 and non-empty payload.
Case Expectation
The connection is failed immediately.
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: i/3y0vrFcFEZERezHakkcg== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: Upgrade Sec-WebSocket-Accept: zZBMujgfVyPATjOIVjNZq0oC5fU= 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 | False | 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 | None | The close reason I sent in close frame (if any). |
| remoteCloseCode | 1002 | The close code the peer sent me in close frame (if any). |
| remoteCloseReason | protocol error: opcode 4 is reserved or invalid | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 51 | 1 | 51 |
| 175 | 1 | 175 |
| Total | 2 | 226 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 29 | 1 | 29 |
| 255 | 1 | 255 |
| Total | 3 | 292 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 4 | 1 |
| 8 | 1 |
| Total | 2 |
000 TX OCTETS: 474554202f6563686f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f
302e382e322d302e31302e390d0a ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772
6164650d0a5365632d576562536f ...
002 TX FRAME : OPCODE=4, FIN=True, RSV=0, PAYLOAD-LEN=23, MASK=c4b497da, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
reserved opcode payload
003 TX OCTETS: 8497c4b497dab6d1e4bfb6c2f2bee4dbe7b9abd0f2fab4d5eeb6abd5f3
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 883103ea70726f746f636f6c206572726f723a206f70636f64652034206973207265736572766564206f7220696e76616c69
64
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=49, MASKED=False, MASK=None
0x03ea70726f746f636f6c206572726f723a206f70636f64652034206973207265736572766564206f7220696e76616c6964
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=a85c57d0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
008 TX OCTETS: 8882a85c57d0abb4
009 TCP DROPPED BY PEER