WebSocket-Node 1.0.27 - Case 9.1.4 : Pass - 293 ms @ 2020-08-28T14:51:24.193Z

Case Description

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

Case Expectation

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

Case Outcome

Received text 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: qFtQWG9Zrl40Y2160IygoA==
Sec-WebSocket-Version: 13

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

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
1460	12	17520
2756	2	5512
2920	17	49640
4216	2	8432
4380	13	56940
5676	2	11352
5815	1	5815
5840	12	70080
7007	1	7007
7136	6	42816
7300	20	146000
8596	3	25788
8760	20	175200
10056	3	30168
10220	24	245280
11516	4	46064
11680	25	292000
12976	6	77856
13140	23	302220
14436	3	43308
14600	18	262800
15896	3	47688
16060	14	224840
17356	3	52068
17520	14	245280
18816	4	75264
18980	1	18980
20276	4	81104
20440	2	40880
21736	1	21736
21900	5	109500
23196	1	23196
23360	3	70080
24820	4	99280
26280	2	52560
27740	2	55480
29200	1	29200
30496	1	30496
30660	2	61320
33416	1	33416
36500	1	36500
40716	1	40716
46720	1	46720
56776	1	56776
64076	1	64076
65536	10	655360
Total	302	4194447

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
251	1	251
4194318	1	4194318
Total	3	4194577

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

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

               0x03e8

004 TX OCTETS: 88820df586b50e1d

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