Autobahn WebSocket Testsuite Report
Autobahn WebSocket

ws@6.2.0 - Case 9.1.6 : Pass - 842 ms @ 2019-03-09T17:18:48.435Z

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.0-0.10.9
Host: 192.168.0.109:9002
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: RD097OgvzbBzwS3DF+PEvw==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: n2yrrFv7E9bZcSs5DUTGc2ToJKg=

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
129622592
1460132192720
275638268
292059172280
4216312648
438044192720
439014390
5676317028
584034198560
7136321408
730031226300
764117641
8596760172
876045394200
10056440224
10195110195
1022040408800
1151612138192
1168045525600
1297610129760
1314057748980
1443615216540
1460048700800
1589617270232
1606046738760
1735624416544
1752055963600
18336118336
1881625470400
1898047892060
2027615304140
20440501022000
2173614304304
2190032700800
2319611255156
2336021490560
2465612295872
2482017421940
2611615391740
2628015394200
2757610275760
2774012332880
2903610290360
2920013379600
3049610304960
3066011337260
319564127824
321204128480
334163100248
335803100740
348763104628
350403105120
36336272672
365004146000
377964151184
379603113880
39256278512
39420139420
40716140716
40880281760
421763126528
42340284680
43800143800
45096290192
46556146556
46720146720
56776156776
58236158236
655362131072
Total113816777359

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
2441244
16777230116777230
Total316777482

Frames Received by Opcode

OpcodeCount
11
81
Total2

Frames Transmitted by Opcode

OpcodeCount
11
81
Total2

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
               302d302e31302e390d0a486f7374 ...
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=bbba091f, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
004 TX OCTETS: 8882bbba091fb852
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