WebSocket-Node 1.0.27 - Case 9.4.3 : Pass - 311 ms @ 2020-08-28T14:51:30.391Z

Case Description

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

Case Expectation

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

Case Outcome

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

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

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	14	20440
2756	2	5512
2920	25	73000
4216	5	21080
4380	33	144540
5676	6	34056
5840	50	292000
7136	6	42816
7300	51	372300
8596	4	34384
8760	37	324120
10056	2	20112
10220	30	306600
11516	1	11516
11680	20	233600
12976	4	51904
13140	12	157680
14307	1	14307
14436	2	28872
14600	11	160600
15896	3	47688
16060	11	176660
17356	6	104136
17520	5	87600
18816	4	75264
18980	1	18980
20440	3	61320
21736	2	43472
21900	3	65700
23196	1	23196
23360	5	116800
24820	1	24820
26116	1	26116
27740	1	27740
29200	1	29200
30660	1	30660
32120	2	64240
35040	2	70080
37796	1	37796
39256	2	78512
42176	1	42176
42340	1	42340
48016	1	48016
51100	1	51100
55316	1	55316
64240	1	64240
65536	5	327680
Total	389	4194447

Octets Transmitted by Chop Size

Chop Size	Count	Octets
6	1	6
8	1	8
251	1	251
1032	4096	4227072
Total	4099	4227337

Frames Received by Opcode

Opcode	Count
2	1
8	1
Total	2

Frames Transmitted by Opcode

Opcode	Count
0	4096
2	1
8	1
Total	4098

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

               0x03e8

004 TX OCTETS: 88825688191e5560

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