ws@6.2.0 - Case 9.1.5 : Pass - 436 ms @ 2019-03-09T17:18:47.997Z

Case Description

Send text message message with payload of length 8 * 2**20 (8M).

Case Expectation

Receive echo'ed text message (with payload as sent).

Case Outcome

Received text message of length 8388608.

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: a6i5PHRNOx2n6t5JPe3e7A==
Sec-WebSocket-Version: 13

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

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
1157	1	1157
1296	1	1296
1460	62	90520
2756	1	2756
2920	25	73000
4216	1	4216
4380	24	105120
4390	1	4390
5676	3	17028
5840	21	122640
7136	2	14272
7300	23	167900
8596	2	17192
8760	19	166440
10056	4	40224
10220	27	275940
11516	7	80612
11680	25	292000
12976	12	155712
13140	23	302220
14436	9	129924
14600	31	452600
15896	4	63584
16035	1	16035
16060	25	401500
17356	12	208272
17520	31	543120
18816	8	150528
18980	24	455520
20276	8	162208
20440	19	388360
21736	6	130416
21900	13	284700
23196	8	185568
23360	14	327040
24656	5	123280
24820	19	471580
26116	7	182812
26280	10	262800
27576	6	165456
27740	9	249660
29036	3	87108
29200	4	116800
30496	6	182976
30660	3	91980
31956	2	63912
32120	1	32120
33416	1	33416
34876	1	34876
35040	2	70080
39256	2	78512
42176	1	42176
43636	1	43636
50936	1	50936
51100	1	51100
53856	1	53856
65536	1	65536
Total	586	8388751

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
244	1	244
8388622	1	8388622
Total	3	8388874

Frames Received by Opcode

Opcode	Count
1	1
8	1
Total	2

Frames Transmitted by Opcode

Opcode	Count
1	1
8	1
Total	2

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

               0x03e8

004 TX OCTETS: 88826eeb3d6e6d03

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