AVR / W5100 / Ethernet - Case 9.3.8 : Pass - 22 ms @ 2025-03-16T00:20:39.632Z

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

HTTP/1.1 101 Switching Protocols
Access-Control-Allow-Origin: *
Connection: Upgrade
Sec-Websocket-Accept: Wsty/cRfPucJaEDr9RPpRXeQ7a8=
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
4	2	8
198	1	198
4096	1	4096
4098	1	4098
4100	4	16400
4101	1	4101
4102	3	12306
4104	4	16416
8196	4	32784
8197	1	8197
8198	1	8198
8201	1	8201
8202	1	8202
8203	1	8203
12297	1	12297
12299	1	12299
12300	2	24600
12303	1	12303
12304	1	12304
24596	1	24596
26774	1	26774
28697	1	28697
28701	2	57402
32798	1	32798
32799	1	32799
32800	3	98400
32802	1	32802
49196	1	49196
49202	3	147606
53297	1	53297
53302	1	53302
57396	1	57396
57398	1	57398
57402	1	57402
57403	1	57403
61498	1	61498
61500	2	123000
61502	1	61502
62075	1	62075
65536	43	2818048
Total	101	4198602

Octets Transmitted by Chop Size

Chop Size	Count	Octets
6	1	6
8	1	8
251	1	251
1048590	4	4194360
Total	7	4194625

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 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=a618958d, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e8

004 TX OCTETS: 8882a618958da5f0

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