Autobahn WebSocket Testsuite Report
Autobahn WebSocket

WebSocket-Node 1.0.27 - Case 9.1.6 : Pass - 801 ms @ 2020-08-28T14:51:24.902Z

Case Description

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

Case Expectation

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

Case Outcome

Received text 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: xsuMOvaBIX8LgfVlh9PjkQ==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: ttHIqliRdsoqcVDJfDqm0hbX/tA=

Closing Behavior

KeyValueDescription
isServerFalseTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeTrueTrue, iff I have initiated closing handshake (that is, did send close first).
failedByMeFalseTrue, 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.
droppedByMeFalseTrue, iff I dropped the TCP connection.
wasCleanTrueTrue, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonNoneWhen wasClean == False, the reason what happened.
wasServerConnectionDropTimeoutFalseWhen we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeoutFalseWhen performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeoutFalseWhen we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode1000The close code I sent in close frame (if any).
localCloseReasonNoneThe close reason I sent in close frame (if any).
remoteCloseCode1000The close code the peer sent me in close frame (if any).
remoteCloseReasonNoneThe close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
414
1291129
1391139
129656480
14605580300
27561233072
292091265720
42161042160
438084367920
567628158928
5840144840960
713623164128
73001681226400
859632275072
87601431252680
992719927
1005618181008
102201241267280
1151621241836
116801071249760
1297618233568
13140931222020
1443621303156
14600691007400
1589612190752
1606053851180
1735610173560
1752048840960
188166112896
1898023436540
20276481104
2044018367920
217368173888
2190028613200
23196246392
2336012280320
24656249312
248207173740
262805131400
27576382728
277405138700
29036258072
292005146000
30496260992
306609275940
31956395868
32120132120
33416133416
33580133580
34876134876
350403105120
36336272672
36500136500
37796275592
37960275920
42176142176
43636143636
46556146556
49476298952
51100151100
52560152560
655362131072
Total156016777359

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
2511251
16777230116777230
Total316777489

Frames Received by Opcode

OpcodeCount
11
81
Total2

Frames Transmitted by Opcode

OpcodeCount
11
81
Total2

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=1afcf142, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
004 TX OCTETS: 88821afcf1421914
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