Autobahn WebSocket Testsuite Report
Autobahn WebSocket

Boost.Beast/189-Sync - Case 12.4.2 : Pass - 569 ms @ 2018-11-09T16:30:01.691Z

Case Description

Send 1000 compressed messages each of payload size 64, auto-fragment to 0 octets. Use default permessage-deflate offer.

Case Expectation

Receive echo'ed messages (with payload as sent). Timeout case after 60 secs.

Case Outcome

Ok, received all echo'ed messages in time.

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: ZTzxwVtKU/GVWo+DV8ycqw==

Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits

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

Upgrade: websocket

Connection: upgrade

Sec-WebSocket-Accept: SJg+gZuMDyD7O41jXDvtAv8K/Uw=

Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover

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
38138
414164
423126
433129
447308
458360
4615690
479423
4815720
4913637
501547700
51562856
52583016
53231219
54251350
55492695
561619016
57784446
58864988
59422478
60281680
61241464
62452790
6313819
647448
65402600
6614924
676402
6813884
2331233
Total100255607

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
40140
43143
454180
463138
474188
485240
498392
50201000
517357
5213676
5316848
5418810152
55532915
56231288
57261482
58221276
59492891
601619660
61784758
62875394
63442772
64251600
65241560
66452970
6713871
687476
69402760
7014980
716426
7213936
3381338
Total100259615

Frames Received by Opcode

OpcodeCount
11000
81
Total1001

Frames Transmitted by Opcode

OpcodeCount
11000
81
Total1001


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
               302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a436f6e6e656374696f6e ...
002 WIRELOG DISABLED
003 CLOSE CONNECTION AFTER 60.000000 sec
004 WIRELOG ENABLED
005 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=c5bdbe20, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
006 TX OCTETS: 8882c5bdbe20c655
007 RX OCTETS: 880203e8
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=False, MASK=None
               0x03e8
009 TCP DROPPED BY PEER