AVR / W5100 / Ethernet - Case 9.3.3 : Pass - 46 ms @ 2025-03-16T00:20:39.450Z

Case Description

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

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 / HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: host.docker.internal:9001
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: v2QwKMK6L/TCXRfYCUf85g==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Access-Control-Allow-Origin: *
Connection: Upgrade
Sec-Websocket-Accept: r/Nq6JIB5tpI7ZIiuG9u4W9DQ5o=
Upgrade: websocket
Date: Sun, 16 Mar 2025 00:20:39 GMT

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	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	7	7
2	11	22
4	13	52
198	1	198
4096	8	32768
4097	10	40970
4098	17	69666
4099	15	61485
4100	85	348500
4101	25	102525
4102	10	41020
4103	2	8206
4104	7	28728
8196	10	81960
8197	2	16394
8198	4	32792
8199	8	65592
8200	20	164000
8201	4	32804
8202	1	8202
8204	3	24612
12296	1	12296
12298	2	24596
12299	4	49196
12300	6	73800
12301	3	36903
12302	3	36906
12304	4	49216
16396	1	16396
16397	1	16397
16398	1	16398
16399	2	32798
16400	7	114800
20499	1	20499
20500	1	20500
20501	1	20501
24599	1	24599
24601	1	24601
28701	1	28701
32800	1	32800
40998	1	40998
57399	1	57399
59575	1	59575
65536	34	2228224
Total	342	4198602

Octets Transmitted by Chop Size

Chop Size	Count	Octets
6	1	6
8	1	8
251	1	251
1032	4096	4227072
Total	4099	4227337

Frames Received by Opcode

Opcode	Count
0	1023
1	1
8	1
Total	1025

Frames Transmitted by Opcode

Opcode	Count
0	4096
1	1
8	1
Total	4098

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e

               322d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a4163636573732d436f6e74726f6c2d41

               6c6c6f772d4f726967696e3a202a ...

002 CLOSE CONNECTION AFTER 100.000000 sec

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

               0x03e8

004 TX OCTETS: 88827c8204937f6a

005 RX OCTETS: 880203e8

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

               0x03e8

007 TCP DROPPED BY PEER