websock secure server - Case 5.16 : Pass - 1 ms @ 2025-09-19T08:55:29.023Z
Case Description
Repeated 2x: Continuation Frame with FIN = false (where there is nothing to continue), then text Message fragmented into 2 fragments.
Case Expectation
The connection is failed immediately, since there is no message to continue.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /wss HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: 127.0.0.1:8889 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: 1kLEi1uCCmRXlm644VLMWQ== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Date: Fri, 19 Sep 2025 08:55:29 GMT Upgrade: websocket Connection: Upgrade Sec-Websocket-Accept: 8AkRo5zp47BDId4L/yQz32COwWQ=
| 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 | 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 dropped the TCP connection without previous WebSocket 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 | False | When we initiated a closing handshake, but the peer did not respond in time, this gets True. |
| localCloseCode | None | The close code I sent in close frame (if any). |
| localCloseReason | None | 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 |
| 166 | 1 | 166 |
| Total | 1 | 166 |
| Chop Size | Count | Octets |
| 15 | 6 | 90 |
| 243 | 1 | 243 |
| Total | 7 | 333 |
| Opcode | Count |
| Total | 0 |
| Opcode | Count |
| 0 | 4 |
| 1 | 2 |
| Total | 6 |
000 TX OCTETS: 474554202f77737320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f30
2e382e322d302e31302e390d0a48 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a204672692c203139205365
7020323032352030383a35353a32 ...
002 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=92722999, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
003 TX OCTETS: 008992722999f40048feff1747eda3
004 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=3dfad50a, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
005 TX OCTETS: 01893dfad50a5b88b46d509fbb7e0f
006 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=b1c073a8, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment3
007 TX OCTETS: 8089b1c073a8d7b212cfdca51ddc82
008 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=6540e3bb, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
009 TX OCTETS: 00896540e3bb033282dc08258dcf54
010 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=44b8f028, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
011 TX OCTETS: 018944b8f02822ca914f29dd9e5c76
012 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=3b438b11, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment3
013 TX OCTETS: 80893b438b115d31ea765626e56508
014 FAIL CONNECTION AFTER 1.000000 sec
015 TCP DROPPED BY PEER