Autobahn WebSocket Testsuite Report
Autobahn WebSocket

Hornbeam - Case 3.6 : Pass - 44 ms @ 2023-08-11T05:15:07.093Z

Case Description

Send Ping with RSV = 6.

Case Expectation

The connection is failed immediately, since RSV must be 0.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET /runCase?case=33&agent=Hornbeam HTTP/1.1
Host: localhost:9001
Upgrade: websocket
Connection: upgrade
Sec-WebSocket-Key: FZRx0Y/8mTFmq4E4NHDe+g==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.8.2-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: IHApI9ALKnza/sb2WZKUu2busFg=


Closing Behavior

KeyValueDescription
isServerTrueTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeFalseTrue, 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.
droppedByMeTrueTrue, 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).
remoteCloseCode1002The close code the peer sent me in close frame (if any).
remoteCloseReasonProtocol ErrorThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
111
1531153
1831183
Total3337

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
15115
2061206
Total3225

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
21
81
Total2


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3333266167656e743d486f726e6265616d20485454502f312e310d0a486f7374
               3a206c6f63616c686f73743a3930 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=2, FIN=True, RSV=6, PAYLOAD-LEN=13, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               Hello, world!
003 TX OCTETS: e20d48656c6c6f2c20776f726c6421
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 88
006 RX OCTETS: 90f345810cf0afd17e9c31ee6f9c29a1498137ee7e8890515e321952b4626b3e2a5d7a3e32125c232c5d6b8890d654b5cad5
               bee5b8b920daa9b938958fa426da ...
007 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=16, MASKED=True, MASK=6633343538313063
               0x03ea50726f746f636f6c204572726f72
008 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
009 TX OCTETS: 880203e8
010 TCP DROPPED BY ME