node-v10.24.1 - Case 5.18 : Pass - 1 ms @ 2023-09-07T20:07:48.972Z
Case Description
Send text Message fragmented into 2 fragments, with both frame opcodes set to text, sent in one chop.
Case Expectation
The connection is failed immediately, since all data frames after the initial data frame must have opcode 0.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=62&agent=node-v10.24.1 HTTP/1.1 Host: 0.0.0.0:9001 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: ymEc1g7nNtLeI4TR5IcoIQ== 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: c1KJ8bWwaz9i3cjIlarGHkAYiHQ=
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 new data frame but previous continuous frame is unfinished | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
75 | 1 | 75 |
256 | 1 | 256 |
Total | 2 | 331 |
Chop Size | Count | Octets |
4 | 1 | 4 |
11 | 2 | 22 |
206 | 1 | 206 |
Total | 4 | 232 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
1 | 2 |
8 | 1 |
Total | 3 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3632266167656e743d6e6f64652d7631302e32342e3120485454502f312e310d
0a486f73743a20302e302e302e30 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
003 TX OCTETS: 0109667261676d656e7431
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
005 TX OCTETS: 8109667261676d656e7432
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 88c51066a637138cf4527303cf4175028659751186537112c7177614c75a7546c4426446d6457510cf58651586547f08d25e
7e13c9426346c045710bc3177915 ...
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=69, MASKED=True, MASK=3130363661363337
0x03ea5265636569766564206e65772064617461206672616d65206275742070726576696f757320636f6e74696e756f7573
206672616d6520697320756e66696e ...
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