WebSocket-Node 1.0.27 - Case 9.4.8 : Pass - 237 ms @ 2020-08-28T14:51:31.542Z

Case Description

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

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: BhjxPY+MTDVlJjLAfvzfGw==
Sec-WebSocket-Version: 13

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

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	6	7776
1460	35	51100
2627	1	2627
2756	6	16536
2920	54	157680
4216	7	29512
4380	56	245280
5676	6	34056
5840	49	286160
7136	3	21408
7300	53	386900
8596	6	51576
8760	40	350400
10056	5	50280
10220	24	245280
11516	5	57580
11680	26	303680
12976	2	25952
13140	18	236520
14575	1	14575
14600	18	262800
15896	3	47688
16060	9	144540
17356	3	52068
17520	5	87600
18980	2	37960
20276	2	40552
20440	6	122640
21900	5	109500
23196	1	23196
23360	3	70080
24656	1	24656
24820	4	99280
26116	1	26116
27740	1	27740
30496	1	30496
33416	1	33416
35040	1	35040
42176	1	42176
43800	3	131400
52396	1	52396
52560	1	52560
65536	1	65536
Total	479	4194447

Octets Transmitted by Chop Size

Chop Size	Count	Octets
6	1	6
8	1	8
251	1	251
1048590	4	4194360
Total	7	4194625

Frames Received by Opcode

Opcode	Count
2	1
8	1
Total	2

Frames Transmitted by Opcode

Opcode	Count
0	4
2	1
8	1
Total	6

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

               0x03e8

004 TX OCTETS: 8882269c4e092574

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