WebSocket-Node 1.0.27 - Case 9.2.5 : Pass - 444 ms @ 2020-08-28T14:51:26.094Z

Case Description

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

Case Expectation

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

Case Outcome

Received binary 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.1-0.10.9
Host: host.docker.internal:8080
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: Mgs07aTL7ZKOtLmIkDzl7Q==
Sec-WebSocket-Version: 13

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

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
139	1	139
1296	3	3888
1460	46	67160
2756	5	13780
2920	55	160600
4216	12	50592
4380	57	249660
5676	9	51084
5840	103	601520
7136	11	78496
7300	98	715400
8596	11	94556
8760	57	499320
10056	14	140784
10220	73	746060
11516	7	80612
11680	51	595680
12976	14	181664
13140	36	473040
14436	2	28872
14600	40	584000
15896	5	79480
16060	24	385440
17356	8	138848
17520	17	297840
18816	2	37632
18980	9	170820
20276	2	40552
20440	6	122640
21607	1	21607
21736	3	65208
21900	10	219000
23196	4	92784
23360	8	186880
24656	2	49312
24820	6	148920
26280	5	131400
27576	1	27576
27740	3	83220
29036	2	58072
29200	2	58400
30496	1	30496
31956	2	63912
32120	1	32120
34876	1	34876
37796	2	75592
37960	1	37960
39256	1	39256
45260	1	45260
65536	3	196608
Total	840	8388751

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
251	1	251
8388622	1	8388622
Total	3	8388881

Frames Received by Opcode

Opcode	Count
2	1
8	1
Total	2

Frames Transmitted by Opcode

Opcode	Count
2	1
8	1
Total	2

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e

               312d302e31302e390d0a486f7374 ...

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

               0x03e8

004 TX OCTETS: 8882ab00bbb3a8e8

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