ws@6.2.0 - Case 9.3.5 : Pass - 173 ms @ 2019-03-09T17:18:51.972Z

Case Description

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

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.0-0.10.9
Host: 192.168.0.109:9002
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: QLkxhnn6thJ/DYDpPLK4NA==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: 83m9qqUuKruS2AvneIcXnMvOTa8=

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	1	4
129	1	129
1460	41	59860
2920	10	29200
4216	1	4216
4380	11	48180
4390	1	4390
5840	8	46720
7136	1	7136
7275	1	7275
7300	16	116800
8596	3	25788
8760	12	105120
9917	1	9917
10056	2	20112
10220	11	112420
11516	4	46064
11680	12	140160
12976	3	38928
13140	7	91980
14436	2	28872
14600	13	189800
15896	5	79480
16060	16	256960
17356	2	34712
17520	6	105120
18816	3	56448
18980	14	265720
20276	4	81104
20440	8	163520
21736	2	43472
21900	8	175200
23196	3	69588
23360	5	116800
24656	3	73968
26116	1	26116
26280	4	105120
27576	1	27576
27740	3	83220
29036	2	58072
29200	1	29200
30496	3	91488
31956	2	63912
32120	2	64240
33416	1	33416
33580	1	33580
34876	1	34876
35040	1	35040
39420	1	39420
40716	1	40716
43636	2	87272
43800	1	43800
45096	2	90192
45260	1	45260
49476	1	49476
64076	1	64076
65536	6	393216
Total	280	4194447

Octets Transmitted by Chop Size

Chop Size	Count	Octets
6	1	6
8	1	8
244	1	244
16392	256	4196352
Total	259	4196610

Frames Received by Opcode

Opcode	Count
1	1
8	1
Total	2

Frames Transmitted by Opcode

Opcode	Count
0	256
1	1
8	1
Total	258

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e

               302d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b

               65740d0a436f6e6e656374696f6e ...

002 CLOSE CONNECTION AFTER 100.000000 sec

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

               0x03e8

004 TX OCTETS: 8882605d21cb63b5

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