WebSocket-Node 1.0.27 - Case 9.2.6 : Pass - 809 ms @ 2020-08-28T14:51:26.545Z

Case Description

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

Case Expectation

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

Case Outcome

Received binary message of length 16777216.

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: KR/KLeeRPFxUBNi2UbfdlQ==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: +SS85DlV/FFVCTYcIvKA70QpdXY=

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	21	27216
1460	126	183960
2756	15	41340
2920	145	423400
4216	20	84320
4380	141	617580
5676	30	170280
5840	239	1395760
7136	24	171264
7300	321	2343300
8596	29	249284
8760	190	1664400
10056	16	160896
10220	150	1533000
11387	1	11387
11516	20	230320
11680	99	1156320
12976	18	233568
13140	81	1064340
14436	10	144360
14600	58	846800
15896	9	143064
16060	48	770880
17356	12	208272
17520	36	630720
18816	6	112896
18980	16	303680
20276	3	60828
20440	10	204400
21736	3	65208
21900	10	219000
23196	2	46392
23360	4	93440
24656	2	49312
24820	3	74460
26116	1	26116
26280	6	157680
27576	1	27576
27740	1	27740
29036	1	29036
30660	2	61320
31956	1	31956
34876	1	34876
35040	2	70080
36336	2	72672
36500	1	36500
37796	1	37796
37960	1	37960
39256	1	39256
40716	1	40716
42176	1	42176
45260	1	45260
49476	1	49476
50936	1	50936
56776	1	56776
65536	1	65536
Total	1950	16777359

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
251	1	251
16777230	1	16777230
Total	3	16777489

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

               0x03e8

004 TX OCTETS: 888241886ea64260

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