ws@6.2.0 - Case 9.4.3 : Pass - 159 ms @ 2019-03-09T17:18:53.327Z

Case Description

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

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: 8LiePQ+mkfOJ/zyENr/CBQ==
Sec-WebSocket-Version: 13

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

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	2	2592
1460	45	65700
2920	24	70080
4216	1	4216
4380	16	70080
5676	1	5676
5840	13	75920
7300	16	116800
8596	1	8596
8760	11	96360
10056	2	20112
10195	1	10195
10220	6	61320
11516	3	34548
11680	4	46720
12976	3	38928
13140	6	78840
14436	1	14436
14600	12	175200
15767	1	15767
15896	6	95376
16060	7	112420
17356	5	86780
17520	8	140160
18816	6	112896
18980	7	132860
20276	2	40552
20440	12	245280
21736	4	86944
21900	11	240900
23196	1	23196
23360	6	140160
24656	5	123280
24820	8	198560
26116	1	26116
26280	3	78840
27576	2	55152
27740	4	110960
29036	1	29036
29200	1	29200
30660	1	30660
32120	1	32120
33416	1	33416
33580	1	33580
35040	1	35040
36336	2	72672
37796	2	75592
39256	1	39256
42340	1	42340
43636	1	43636
43800	2	87600
49640	1	49640
55316	1	55316
56776	1	56776
58236	1	58236
65536	5	327680
Total	294	4194447

Octets Transmitted by Chop Size

Chop Size	Count	Octets
6	1	6
8	1	8
244	1	244
1032	4096	4227072
Total	4099	4227330

Frames Received by Opcode

Opcode	Count
2	1
8	1
Total	2

Frames Transmitted by Opcode

Opcode	Count
0	4096
2	1
8	1
Total	4098

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

               0x03e8

004 TX OCTETS: 88823d7f67e83e97

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