Hornbeam - Case 2.5 : Pass - 1003 ms @ 2023-08-10T21:34:50.086Z
Case Description
Send ping with binary payload of 126 octets.
Case Expectation
Connection is failed immediately (1002/Protocol Error), since control frames are only allowed to have payload up to and including 125 octets..
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
The connection was failed by the wrong endpoint (FAILED)
GET /runCase?case=21&agent=Hornbeam HTTP/1.1 Host: localhost:9001 Upgrade: websocket Connection: upgrade Sec-WebSocket-Key: 5e0gG5mCIev1qcA6hHXz1Q== 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: xhrE7D+ZfluuL2AdymQ0xHg1BCI=
Key | Value | Description |
isServer | True | True, iff I (the fuzzer) am a server, and the peer is a client. |
closedByMe | True | True, iff I have initiated closing handshake (that is, did send close first). |
failedByMe | True | True, 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. |
droppedByMe | True | True, iff I dropped the TCP connection. |
wasClean | True | True, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility). |
wasNotCleanReason | None | When wasClean == False, the reason what happened. |
wasServerConnectionDropTimeout | False | When we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True. |
wasOpenHandshakeTimeout | False | When performing the opening handshake, but the peer did not finish in time, this gets True. |
wasCloseHandshakeTimeout | False | When we initiated a closing handshake, but the peer did not respond in time, this gets True. |
localCloseCode | 1001 | The close code I sent in close frame (if any). |
localCloseReason | Going Away | The close reason I sent in close frame (if any). |
remoteCloseCode | 1001 | The close code the peer sent me in close frame (if any). |
remoteCloseReason | Going Away | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
18 | 1 | 18 |
183 | 1 | 183 |
Total | 2 | 201 |
Chop Size | Count | Octets |
14 | 1 | 14 |
130 | 1 | 130 |
206 | 1 | 206 |
Total | 3 | 350 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
8 | 1 |
9 | 1 |
Total | 2 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3231266167656e743d486f726e6265616d20485454502f312e310d0a486f7374
3a206c6f63616c686f73743a3930 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=126, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0xfefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe
fefefefefefefefefefefefefefefe ...
003 TX OCTETS: 897e007efefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe
fefefefefefefefefefefefefefe ...
004 FAIL CONNECTION AFTER 1.000000 sec
005 FAILING CONNECTION
006 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e9476f696e672041776179
007 TX OCTETS: 880c03e9476f696e672041776179
008 RX OCTETS: 888cc04e44e0c3a7038fa92023c081392599
009 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=12, MASKED=True, MASK=6330346534346530
0x03e9476f696e672041776179
010 TCP DROPPED BY ME