websock-client - Case 9.2.6 : Pass - 335 ms @ 2026-06-02T16:11:19.320Z

Case Description

Send binary message message with payload of length 16 * 2**20 (16M).

Case Expectation

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

Case Outcome

Received binary message of length 16777216.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET /runCase?case=258&agent=websock-client HTTP/1.1
Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=15
Upgrade: websocket
Host: 127.0.0.1:9001
Connection: Upgrade
Sec-Websocket-Version: 13
Sec-Websocket-Key: AW7a2754AAs0C/boZJikRg==
Cache-Control: no-cache

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/25.10.1-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: UgBGEK7mW8ueENUjY9O/nObG7fc=

Closing Behavior

Key	Value	Description
isServer	True	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	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	1000	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
8	1	8
288	1	288
650	2	1300
756	2	1512
4202	1	4202
5646	1	5646
7224	1	7224
9230	1	9230
11384	1	11384
13326	1	13326
14350	1	14350
15374	1	15374
29696	9	267264
30720	2	61440
33792	18	608256
46080	1	46080
48128	1	48128
49664	1	49664
49964	1	49964
50176	48	2408448
51214	2	102428
56320	4	225280
62464	1	62464
63488	6	380928
64794	2	129588
64900	2	129800
65536	185	12124160
Total	297	16777736

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
208	1	208
16777226	1	16777226
Total	3	16777438

Frames Received by Opcode

Opcode	Count
0	15
2	1
8	1
Total	17

Frames Transmitted by Opcode

Opcode	Count
2	1
8	1
Total	2

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323538266167656e743d776562736f636b2d636c69656e7420485454502f312e

               310d0a5365632d576562736f636b ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f32352e31 ...

002 CLOSE CONNECTION AFTER 100.000000 sec

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

               0x03e8

004 TX OCTETS: 880203e8

005 RX OCTETS: 8882770ce5ee74e4

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

               0x03e8

007 TCP DROPPED BY ME