Autobahn WebSocket Testsuite Report
Autobahn WebSocket

Boost.Beast/189-Sync - Case 9.2.3 : Pass - 17 ms @ 2018-11-09T16:24:36.094Z

Case Description

Send binary message message with payload of length 1 * 2**20 (1M).

Case Expectation

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

Case Outcome

Received binary message of length 1048576.

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: 127.0.0.1:8080

Upgrade: WebSocket

Connection: Upgrade

Pragma: no-cache

Cache-Control: no-cache

Sec-WebSocket-Key: VYXtE1/CPfdG64EFCGp3Aw==

Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols

Upgrade: websocket

Connection: upgrade

Sec-WebSocket-Accept: XTHRtrnnziUwu2zUaiuCdzJb0cw=

Server: Boost.Beast/189-Sync


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
1591159
275612756
276612766
10220110220
14600114600
16224116224
18816237632
34876134876
40880140880
41356141356
42340142340
43800287600
46720293440
51100151100
54020154020
627802125560
655366393216
Total271048749

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
2401240
104859011048590
Total31048838

Frames Received by Opcode

OpcodeCount
21
81
Total2

Frames Transmitted by Opcode

OpcodeCount
21
81
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
               302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a436f6e6e656374696f6e ...
002 CLOSE CONNECTION AFTER 10.000000 sec
003 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=031dd1c0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
004 TX OCTETS: 8882031dd1c000f5
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