ws - Case 9.2.4 : Pass - 42 ms @ 2025-03-16T00:15:14.195Z

Case Description

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

Case Expectation

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

Case Outcome

Received binary message of length 4194304.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET /runCase?case=256&agent=ws HTTP/1.1
Host: localhost:9001
User-Agent: Go-http-client/1.1
Connection: Upgrade
Sec-WebSocket-Key: mNmaepxbeSmnHgiV9D82+Q==
Sec-WebSocket-Version: 13
Upgrade: websocket

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: M1zy+Cr4ol2FFMu/99oXT6D0kc8=

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
1	2	2
7	3	21
210	1	210
4100	3	12300
4102	11	45122
4103	13	53339
4104	28	114912
4105	8	32840
4106	16	65696
4107	2	8214
4108	13	53404
4110	9	36990
4111	3	12333
4112	15	61680
8200	18	147600
8201	9	73809
8202	4	32808
8204	6	49224
8205	2	16410
8206	6	49236
8208	23	188784
8209	4	32836
8210	5	41050
8212	2	16424
8216	3	24648
12304	3	36912
12308	1	12308
12310	1	12310
12311	2	24622
12312	3	36936
12319	1	12319
12320	1	12320
16409	3	49227
16412	2	32824
16416	2	32832
16419	2	32838
16422	1	16422
20520	1	20520
20521	1	20521
21150	1	21150
24616	1	24616
24630	1	24630
28728	1	28728
41042	1	41042
57455	1	57455
57458	1	57458
65536	37	2424832
Total	277	4202714

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
206	1	206
4194314	1	4194314
Total	3	4194524

Frames Received by Opcode

Opcode	Count
0	1023
2	1
8	1
Total	1025

Frames Transmitted by Opcode

Opcode	Count
2	1
8	1
Total	2

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323536266167656e743d777320485454502f312e310d0a486f73743a206c6f63

               616c686f73743a393030310d0a55 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

002 CLOSE CONNECTION AFTER 10.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: 88

006 RX OCTETS: 82b093002ab37b

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

               0x03e8

008 TCP DROPPED BY ME