ws@6.2.0 - Case 9.4.8 : Pass - 157 ms @ 2019-03-09T17:18:54.170Z

Case Description

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

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

HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: yiRIyxA0p17gRH/XpMqtCNp+9iw=

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	61	89060
2756	1	2756
2920	13	37960
4380	16	70080
4390	1	4390
5676	2	11352
5840	10	58400
7136	3	21408
7300	15	109500
8457	1	8457
8596	1	8596
8760	15	131400
10056	1	10056
10220	14	143080
11516	3	34548
11655	1	11655
11680	14	163520
12976	3	38928
13140	12	157680
14436	4	57744
14600	7	102200
15896	5	79480
16060	12	192720
17356	4	69424
17520	13	227760
18816	5	94080
18980	14	265720
20276	4	81104
20440	12	245280
21736	5	108680
21900	4	87600
23196	3	69588
23360	8	186880
24656	4	98624
24820	2	49640
26116	1	26116
26280	3	78840
27576	1	27576
29036	1	29036
29200	2	58400
30660	1	30660
31956	1	31956
32120	3	96360
33580	2	67160
34876	1	34876
35040	1	35040
36336	1	36336
37796	3	113388
37960	1	37960
39256	1	39256
39420	1	39420
46556	1	46556
49476	1	49476
56940	1	56940
64076	1	64076
65536	1	65536
Total	324	4194447

Octets Transmitted by Chop Size

Chop Size	Count	Octets
6	1	6
8	1	8
244	1	244
1048590	4	4194360
Total	7	4194618

Frames Received by Opcode

Opcode	Count
2	1
8	1
Total	2

Frames Transmitted by Opcode

Opcode	Count
0	4
2	1
8	1
Total	6

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

               0x03e8

004 TX OCTETS: 88828a573b5a89bf

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