ws@6.2.0 - Case 9.3.2 : Pass - 263 ms @ 2019-03-09T17:18:51.305Z

Case Description

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

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: B4VqnMQYogGNlunb+R8wsA==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: 8E7MUjIwzcyfzj8MBzn08/Y8Ylg=

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
10	1	10
129	1	129
1296	3	3888
1460	32	46720
2920	13	37960
4380	16	70080
5676	2	11352
5840	11	64240
7300	9	65700
8760	11	96360
10195	1	10195
10220	7	71540
11516	4	46064
11680	13	151840
12976	5	64880
13140	12	157680
14436	2	28872
14600	15	219000
15896	5	79480
16060	12	192720
17356	2	34712
17520	12	210240
18816	6	112896
18980	12	227760
20276	4	81104
20440	8	163520
21597	1	21597
21736	7	152152
21900	12	262800
23196	1	23196
23360	6	140160
24656	1	24656
24820	1	24820
27576	1	27576
27740	3	83220
29036	2	58072
30496	2	60992
30660	3	91980
32120	1	32120
33416	1	33416
33580	1	33580
34876	1	34876
36336	1	36336
37960	2	75920
43636	1	43636
45096	1	45096
50936	1	50936
64076	1	64076
65536	8	524288
Total	279	4194447

Octets Transmitted by Chop Size

Chop Size	Count	Octets
6	1	6
8	1	8
244	1	244
264	16384	4325376
Total	16387	4325634

Frames Received by Opcode

Opcode	Count
1	1
8	1
Total	2

Frames Transmitted by Opcode

Opcode	Count
0	16384
1	1
8	1
Total	16386

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

               0x03e8

004 TX OCTETS: 8882505e9dff53b6

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