Autobahn WebSocket Testsuite Report
Autobahn WebSocket

ws@6.2.0 - Case 9.3.3 : Pass - 174 ms @ 2019-03-09T17:18:51.572Z

Case Description

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

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


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
14602637960
275612756
2920720440
4216312648
4380417520
439014390
5676211352
58401164240
713617136
73001073000
876015131400
10220551100
11377111377
11516223032
11680558400
12976225952
1314012157680
14436228872
1460010146000
15896347688
160608128480
175208140160
18816594080
189809170820
202765101380
204407143080
217365108680
219007153300
23196123196
233606140160
248209223380
26116252232
27576255152
27740255480
29036129036
29200129200
30496130496
30635130635
30660130660
31956395868
32120264240
33416266832
33580133580
34876134876
35040270080
37796137796
37960275920
39256278512
40880140880
42176142176
42340142340
45096145096
45260145260
46556146556
48180148180
49476298952
49640149640
55316155316
56776156776
62616162616
655365327680
Total2424194447

Octets Transmitted by Chop Size

Chop SizeCountOctets
616
818
2441244
103240964227072
Total40994227330

Frames Received by Opcode

OpcodeCount
11
81
Total2

Frames Transmitted by Opcode

OpcodeCount
04096
11
81
Total4098


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=a38e1cdd, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
004 TX OCTETS: 8882a38e1cdda066
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