ws - Case 9.3.8 : Pass - 20 ms @ 2025-03-16T00:15:14.766Z

Case Description

Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 1M.

Case Expectation

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

Case Outcome

Received text message of length 4194304.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET /runCase?case=266&agent=ws HTTP/1.1
Host: localhost:9001
User-Agent: Go-http-client/1.1
Connection: Upgrade
Sec-WebSocket-Key: uliZPTN1OjrpaC3yEVxw3A==
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: k+A6/kvcOX/n/FUCnxy/7U1qrXI=

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	1	1
2	1	2
7	1	7
210	1	210
4104	1	4104
16418	1	16418
20518	1	20518
20522	1	20522
28730	1	28730
28735	1	28735
32832	1	32832
32840	2	65680
36928	1	36928
36929	2	73858
36932	1	36932
36934	1	36934
36936	1	36936
36937	1	36937
36940	3	110820
41032	1	41032
41036	2	82072
41038	1	41038
41040	1	41040
41041	1	41041
41042	2	82084
41043	1	41043
41048	1	41048
45137	1	45137
45140	1	45140
45143	1	45143
45146	1	45146
45148	1	45148
46609	1	46609
47448	1	47448
49241	1	49241
49242	1	49242
49246	1	49246
49247	1	49247
49250	2	98500
49251	1	49251
49256	1	49256
53348	1	53348
53354	1	53354
57452	1	57452
57454	1	57454
57457	1	57457
57458	1	57458
61560	1	61560
63095	1	63095
64200	1	64200
65536	30	1966080
Total	87	4202714

Octets Transmitted by Chop Size

Chop Size	Count	Octets
2	1	2
4	1	4
206	1	206
1048586	4	4194344
Total	7	4194556

Frames Received by Opcode

Opcode	Count
0	1023
1	1
8	1
Total	1025

Frames Transmitted by Opcode

Opcode	Count
0	4
1	1
8	1
Total	6

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323636266167656e743d777320485454502f312e310d0a486f73743a206c6f63

               616c686f73743a393030310d0a55 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

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: 88

006 RX OCTETS: 82d407ceabd7ef

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

               0x03e8

008 TCP DROPPED BY ME