node-v12.22.12 - Case 5.13 : Pass - 5 ms @ 2023-09-07T20:08:43.740Z
Case Description
Send unfragmented Text Message after Continuation Frame with FIN = false, where there is nothing to continue, sent in per-frame chops.
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 /runCase?case=57&agent=node-v12.22.12 HTTP/1.1 Host: 0.0.0.0:9001 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: ZYBtuTzcKkaB5qkkUxj5Ew== Sec-WebSocket-Version: 13 Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
HTTP/1.1 101 Switching Protocols Server: AutobahnTestSuite/0.8.2-0.10.9 X-Powered-By: AutobahnPython/0.10.9 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: RYSuiDJScUgdbHiV/txuNHN2Mo4=
Key | Value | Description |
isServer | True | 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 | True | 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 | Received unexpected continuation frame | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
46 | 1 | 46 |
257 | 1 | 257 |
Total | 2 | 303 |
Chop Size | Count | Octets |
4 | 1 | 4 |
15 | 1 | 15 |
26 | 1 | 26 |
206 | 1 | 206 |
Total | 4 | 251 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
0 | 1 |
1 | 1 |
8 | 1 |
Total | 3 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3537266167656e743d6e6f64652d7631322e32322e313220485454502f312e31
0d0a486f73743a20302e302e302e ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=24, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
non-continuation payload
003 TX OCTETS: 00186e6f6e2d636f6e74696e756174696f6e207061796c6f6164
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
Hello, world!
005 FAIL CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 810d48656c6c6f2c20776f726c6421
007 RX OCTETS: 88a82d2906412ec354244e4c6f37484d2634434c7e31484a72244909652e435d6f2f58487228424726275f486b24
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=40, MASKED=True, MASK=3264323930363431
0x03ea526563656976656420756e657870656374656420636f6e74696e756174696f6e206672616d65
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
010 TX OCTETS: 880203e8
011 TCP DROPPED BY ME