Autobahn WebSocket Testsuite Report
Autobahn WebSocket

non-tls - Case 9.5.6 : Pass - 401 ms @ 2021-07-05T07:52:10.129Z

Case Description

Send text message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 2048 octets.

Case Expectation

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

Case Outcome

Received text message of length 1048576.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET /echo/message HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: localhost:9998
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: O5h+Zj0SjwQcoyCBPz5/lA==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Content-Length: 0
Date: Mon, 05 Jul 2021 07:52:10 GMT
Server: nbio
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Accept: gKvZOutngEdYJ1EObkDG6vus7eI=


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
1991199
25560125560
41000141000
6553615983040
Total191049803

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
14114
2521252
20485121048576
Total5151048850

Frames Received by Opcode

OpcodeCount
0255
11
81
Total257

Frames Transmitted by Opcode

OpcodeCount
11
81
Total2


Wire Log

000 TX OCTETS: 474554202f6563686f2f6d65737361676520485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465
               737453756974652f302e382e322d ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e74656e742d4c656e6774683a20
               300d0a446174653a204d6f6e2c20 ...
002 CLOSE CONNECTION AFTER 1000.000000 sec
003 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=4a93a5ac, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
004 TX OCTETS: 88824a93a5ac497b
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