Case Expectation

Connection is failed immediately (1002/Protocol Error), since control frames are only allowed to have payload up to and including 125 octets..

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

Opening Handshake

GET /runCase?case=21&agent=node-v16.20.2 HTTP/1.1 Host: 0.0.0.0:9001 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: ikFADyeDONlG+BqlzMENFw== Sec-WebSocket-Version: 13 Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits

Closing Behavior

Wire Statistics

Octets Received by Chop Size

Octets Transmitted by Chop Size

Frames Received by Opcode

Frames Transmitted by Opcode

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3231266167656e743d6e6f64652d7631362e32302e3220485454502f312e310d

               0a486f73743a20302e302e302e30 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

002 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=126, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0xfefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe

               fefefefefefefefefefefefefefefe ...

003 TX OCTETS: 897e007efefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe

               fefefefefefefefefefefefefefe ...

004 FAIL CONNECTION AFTER 1.000000 sec

005 RX OCTETS: 88b57cb3e4007f59b6651fd68d7619d7c46313dd907213dfc4660ed289655cdb857615dd832008dc8b2010dc8a675cc38579

               10dc85644693d5324a

006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=53, MASKED=True, MASK=3763623365343030

               0x03ea526563656976656420636f6e74726f6c206672616d6520686176696e6720746f6f206c6f6e67207061796c6f61643a

20313236

007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e8

008 TX OCTETS: 880203e8

009 TCP DROPPED BY ME

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 control frame having too long payload: 126	The close reason the peer sent me in close frame (if any).

Chop Size	Count	Octets
59	1	59
256	1	256
Total	2	315

Chop Size	Count	Octets
4	1	4
130	1	130
206	1	206
Total	3	340