ws@6.2.0 - Case 9.4.4 : Pass - 178 ms @ 2019-03-09T17:18:53.489Z

Case Description

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

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: fmRa+0KSjNYZdPoiL9CX7g==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: vXe6K6N+RYjZtWHCeqP6LPSfZ1g=

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
1296	1	1296
1460	36	52560
2756	2	5512
2895	1	2895
2920	17	49640
4380	13	56940
4390	1	4390
5840	11	64240
7136	5	35680
7300	17	124100
8596	2	17192
8760	11	96360
10056	4	40224
10220	10	102200
11516	3	34548
11680	13	151840
12976	2	25952
13140	9	118260
14436	3	43308
14600	16	233600
15896	3	47688
16060	17	273020
17356	9	156204
17520	12	210240
18816	3	56448
18980	8	151840
20276	4	81104
20440	8	163520
21736	1	21736
21900	11	240900
23196	4	92784
23360	4	93440
24656	2	49312
24820	4	99280
27740	1	27740
29200	3	87600
30496	1	30496
30660	2	61320
31956	1	31956
32120	1	32120
33580	1	33580
34876	2	69752
35040	1	35040
36197	1	36197
36336	1	36336
37796	1	37796
37960	2	75920
39420	2	78840
40716	1	40716
42176	1	42176
48016	1	48016
49640	1	49640
51100	1	51100
52396	2	104792
53856	1	53856
65536	2	131072
Total	299	4194447

Octets Transmitted by Chop Size

Chop Size	Count	Octets
6	1	6
8	1	8
244	1	244
4104	1024	4202496
Total	1027	4202754

Frames Received by Opcode

Opcode	Count
2	1
8	1
Total	2

Frames Transmitted by Opcode

Opcode	Count
0	1024
2	1
8	1
Total	1026

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

               0x03e8

004 TX OCTETS: 8882adbfe642ae57

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