AVR / W5100 / Ethernet - Case 9.2.4 : Pass - 33 ms @ 2025-03-16T00:20:39.023Z

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

HTTP/1.1 101 Switching Protocols
Access-Control-Allow-Origin: *
Connection: Upgrade
Sec-Websocket-Accept: 34FO89z3I5tICAVYcCGe3nJgxeI=
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	6	6
2	36	72
3	11	33
4	21	84
198	1	198
4096	9	36864
4097	1	4097
4098	20	81960
4099	126	516474
4100	77	315700
4101	35	143535
4102	36	147672
4103	3	12309
4104	20	82080
8196	27	221292
8197	10	81970
8198	10	81980
8199	7	57393
8200	25	205000
8201	5	41005
8202	5	41010
8203	3	24609
8204	6	49224
12296	6	73776
12297	3	36891
12298	6	73788
12299	5	61495
12300	5	61500
12301	2	24602
12302	2	24604
12303	1	12303
16398	8	131184
16399	2	32798
16400	5	82000
16401	1	16401
20496	1	20496
20497	1	20497
20499	1	20499
20500	4	82000
20502	2	41004
20504	1	20504
24596	2	49192
24599	1	24599
28698	1	28698
33636	1	33636
41004	1	41004
57524	1	57524
65536	15	983040
Total	578	4198602

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
251	1	251
4194318	1	4194318
Total	3	4194577

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 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e

               322d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a4163636573732d436f6e74726f6c2d41

               6c6c6f772d4f726967696e3a202a ...

002 CLOSE CONNECTION AFTER 10.000000 sec

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

               0x03e8

004 TX OCTETS: 8882553f7f2c56d7

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