websock server - Case 5.15 : Pass - 3 ms @ 2026-05-07T18:09:43.266Z
Case Description
Send text Message fragmented into 2 fragments, then Continuation Frame with FIN = false where there is nothing to continue, then unfragmented Text Message, all sent in one chop.
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': [('message', u'fragment1fragment2', False)], 'NON-STRICT': []}
Observed:
[('message', u'fragment1fragment2', False)]
Case Closing Behavior
Connection was properly closed (OK)
GET /ws HTTP/1.1 User-Agent: AutobahnTestSuite/25.10.1-0.10.9 Host: 127.0.0.1:8888 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: bLEGQjL+h9r16KUhTgm9pw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Date: Thu, 07 May 2026 18:09:43 GMT Connection: Upgrade Upgrade: websocket Sec-Websocket-Accept: qSYbTqLIjw3K2WLV53DVhNBxbck=
| 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 |
| 20 | 1 | 20 |
| 166 | 1 | 166 |
| Total | 2 | 186 |
| Chop Size | Count | Octets |
| 15 | 4 | 60 |
| 244 | 1 | 244 |
| Total | 5 | 304 |
| Opcode | Count |
| 1 | 1 |
| Total | 1 |
| Opcode | Count |
| 0 | 2 |
| 1 | 2 |
| Total | 4 |
000 TX OCTETS: 474554202f777320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f3235
2e31302e312d302e31302e390d0a ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205468752c203037204d61
7920323032362031383a30393a34 ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=e2df54c9, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
003 TX OCTETS: 0189e2df54c984ad35ae8fba3abdd3
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=97f3b339, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
005 TX OCTETS: 808997f3b339f181d25efa96dd4da5
006 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=12d4ce08, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment3
007 TX OCTETS: 008912d4ce0874a6af6f7fb1a07c21
008 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=fb00083b, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment4
009 TX OCTETS: 8189fb00083b9d72695c9665664fcf
010 FAIL CONNECTION AFTER 1.000000 sec
011 RX OCTETS: 8112667261676d656e7431667261676d656e7432
012 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=18, MASKED=False, MASK=None
fragment1fragment2
013 TCP DROPPED BY PEER