ws - Case 9.5.1 : Pass - 251 ms @ 2025-03-16T00:15:15.101Z

Case Description

Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 64 octets.

Case Expectation

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

Case Outcome

Received text message of length 1048576.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET /runCase?case=277&agent=ws HTTP/1.1
Host: localhost:9001
User-Agent: Go-http-client/1.1
Connection: Upgrade
Sec-WebSocket-Key: Q2g40GQfvw8ao5NVSdg+Og==
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: Gk3lG6asF9gEHKo4Ij23G/3VcA8=

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	3	6
3	1	3
4	2	8
8	8	64
210	1	210
4096	2	8192
4100	2	8200
4102	1	4102
4103	3	12309
4104	20	82080
4105	3	12315
4106	6	24636
4107	1	4107
4108	2	8216
4110	3	12330
4112	5	20560
8200	2	16400
8201	1	8201
8202	3	24606
8204	2	16408
8205	1	8205
8206	9	73854
8207	3	24621
8208	11	90288
8209	1	8209
8210	4	32840
8212	2	16424
8215	2	16430
8216	4	32864
12304	4	49216
12305	4	49220
12306	2	24612
12308	2	24616
12309	1	12309
12310	3	36930
12311	3	36933
12312	4	49248
12320	1	12320
16408	1	16408
16409	1	16409
16410	1	16410
16412	1	16412
16414	2	32828
16415	1	16415
16416	1	16416
16417	1	16417
16418	1	16418
24616	1	24616
Total	144	1050842

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
10	1	10
64	16384	1048576
206	1	206
Total	16387	1048796

Frames Received by Opcode

Opcode	Count
0	255
1	1
8	1
Total	257

Frames Transmitted by Opcode

Opcode	Count
1	1
8	1
Total	2

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323737266167656e743d777320485454502f312e310d0a486f73743a206c6f63

               616c686f73743a393030310d0a55 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

002 CLOSE CONNECTION AFTER 1000.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: 8882f597ac9ff67f

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

               0x03e8

007 TCP DROPPED BY ME