websock server - Case 9.1.1 : Pass - 3 ms @ 2025-11-26T12:34:48.258Z

Case Description

Send text message message with payload of length 64 * 2**10 (64k).

Case Expectation

Receive echo'ed text message (with payload as sent).

Case Outcome

Received text message of length 65536.

Expected:
{}

Observed:
[]

Case Closing Behavior

The spec requires the connection to be failed cleanly here (UNCLEAN)

Opening Handshake

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: dfY73y42YrS/CrI9ZCR4GA==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Date: Wed, 26 Nov 2025 12:34:48 GMT
Connection: Upgrade
Upgrade: websocket
Sec-Websocket-Accept: ZV8TWympcpycpSK+jMxz509jb9o=

Closing Behavior

Key	Value	Description
isServer	False	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	True	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	1000	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).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
10	1	10
166	1	166
65536	1	65536
Total	3	65712

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
244	1	244
65550	1	65550
Total	3	65802

Frames Received by Opcode

Opcode	Count
1	1
Total	1

Frames Transmitted by Opcode

Opcode	Count
1	1
8	1
Total	2

Wire Log

000 TX OCTETS: 474554202f777320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f3235

               2e31302e312d302e31302e390d0a ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205765642c203236204e6f

               7620323032352031323a33343a34 ...

002 CLOSE CONNECTION AFTER 10.000000 sec

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

               0x03e8

004 TX OCTETS: 8882c8845b8ccb6c

005 TCP DROPPED BY PEER