ws@6.2.0 - Case 9.3.8 : Pass - 171 ms @ 2019-03-09T17:18:52.511Z

Case Description

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

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: mSNEejiZn0ihgRaFP/UWpQ==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: 9EiVZNA+AISAAH2E+RpyjGe8b/Y=

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	33	48180
2756	1	2756
2920	7	20440
4216	1	4216
4380	8	35040
4390	1	4390
5676	1	5676
5840	3	17520
7136	2	14272
7300	12	87600
8596	1	8596
8760	12	105120
10056	1	10056
10220	13	132860
11516	7	80612
11680	14	163520
12976	1	12976
13140	10	131400
14436	1	14436
14575	1	14575
14600	6	87600
15896	2	31792
16060	7	112420
17356	5	86780
17520	10	175200
18677	1	18677
18816	2	37632
18980	9	170820
20276	4	81104
20440	11	224840
21736	5	108680
21900	6	131400
23360	4	93440
24656	5	123280
24820	8	198560
26116	4	104464
26280	2	52560
27576	3	82728
27740	5	138700
29036	2	58072
29200	1	29200
30496	1	30496
30660	4	122640
33416	1	33416
33580	3	100740
35040	1	35040
36500	1	36500
37796	1	37796
39420	1	39420
40880	1	40880
42176	2	84352
43800	1	43800
45096	1	45096
50936	1	50936
51100	1	51100
58236	1	58236
59696	1	59696
64076	1	64076
65536	3	196608
Total	261	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
1	1
8	1
Total	2

Frames Transmitted by Opcode

Opcode	Count
0	4
1	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=bfdc9d95, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e8

004 TX OCTETS: 8882bfdc9d95bc34

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