wsgo fuzzing client - Case 4.2.3 : Pass - 2001 ms @ 2025-03-31T15:46:35.648Z
Case Description
Send small text message, then send frame with reserved control Opcode = 13, then send Ping.
Case Expectation
Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': [('message', u'Hello, world!', False)], 'NON-STRICT': []}
Observed:
[('message', u'Hello, world!', False)]
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: NC6rNSZWdEICIdSD5SVEFA== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: Upgrade Sec-Websocket-Accept: CTgkwnVsFCK3xHN5gbZ8/Hc6+1c= 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 | 1001 | The close code I sent in close frame (if any). |
| localCloseReason | Going Away | 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 |
| 15 | 1 | 15 |
| 129 | 1 | 129 |
| Total | 2 | 144 |
| Chop Size | Count | Octets |
| 6 | 2 | 12 |
| 18 | 1 | 18 |
| 19 | 1 | 19 |
| 240 | 1 | 240 |
| Total | 5 | 289 |
| Opcode | Count |
| 1 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 1 |
| 8 | 1 |
| 9 | 1 |
| 13 | 1 |
| Total | 4 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
322d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772
6164650d0a5365632d576562736f ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=2e4cb573, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
003 TX OCTETS: 818d2e4cb5736629d91f41609504413ed9170f
004 TX FRAME : OPCODE=13, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=0838b61f, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
005 TX OCTETS: 8d800838b61f
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=d8f13f05, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 8980d8f13f05
008 FAIL CONNECTION AFTER 1.000000 sec
009 RX OCTETS: 810d48656c6c6f2c20776f726c6421
010 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASKED=False, MASK=None
Hello, world!
011 FAILING CONNECTION
012 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=d7cf05bd, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e9476f696e672041776179
013 TX OCTETS: 888cd7cf05bdd42642d2bea1629d96b864c4
014 TCP DROPPED BY ME