wsgo fuzzing client - Case 5.1 : Fail - 2002 ms @ 2025-03-31T15:46:39.658Z
Case Description
Send Ping fragmented into 2 fragments.
Case Expectation
Connection is failed immediately, since control message MUST NOT be fragmented.
Case Outcome
Actual events differ from any expected.
Expected:
{'OK': []}
Observed:
[('pong', u'fragment1')]
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: BIDwLFrn6LFzttUeR0OPmQ== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: Upgrade Sec-Websocket-Accept: 4d+te9DX0Za1RJkstrNP9aOtH2o= 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 |
11 | 1 | 11 |
129 | 1 | 129 |
Total | 2 | 140 |
Chop Size | Count | Octets |
15 | 2 | 30 |
18 | 1 | 18 |
240 | 1 | 240 |
Total | 4 | 288 |
Opcode | Count |
10 | 1 |
Total | 1 |
Opcode | Count |
0 | 1 |
8 | 1 |
9 | 1 |
Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
322d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772
6164650d0a5365632d576562736f ...
002 TX FRAME : OPCODE=9, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=4e7f2189, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
003 TX OCTETS: 09894e7f2189280d40ee231a4ffd7f
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=27e20f68, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
005 TX OCTETS: 808927e20f6841906e0f4a87611c15
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 8a09667261676d656e7431
008 RX FRAME : OPCODE=10, FIN=True, RSV=0, PAYLOAD-LEN=9, MASKED=False, MASK=None
fragment1
009 FAILING CONNECTION
010 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=3e455d3f, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e9476f696e672041776179
011 TX OCTETS: 888c3e455d3f3dac1a50572b3a1f7f323c46
012 TCP DROPPED BY ME