Hornbeam - Case 7.9.5 : Fail - 6 ms @ 2023-08-10T21:35:52.276Z

Case Description
Send close with invalid close code 1006

Case Expectation
Clean close with protocol error code or drop TCP

Case Outcome
The close code should have been 1002 or empty
Expected:
{'OK': []}
Observed:
[]

Case Closing Behavior
The close code should have been 1002 or empty (WRONG CODE)

## Opening Handshake

    GET /runCase?case=240&agent=Hornbeam HTTP/1.1
    Host: localhost:9001
    Upgrade: websocket
    Connection: upgrade
    Sec-WebSocket-Key: utRVauK3BrKpmmvMvjmr6g==
    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: vH7Gj2lj04JSmv1lUeyNDdxSR2M=

## Closing Behavior

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 | False | 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 | 1006 | The close code I sent in close frame (if any).
localCloseReason | None | The close reason I sent in close frame (if any).
remoteCloseCode | 1006 | The close code the peer sent me in close frame (if any).
remoteCloseReason | None | The close reason the peer sent me in close frame (if any).

## Wire Statistics

### Octets Received by Chop Size

Chop Size | Count | Octets
8 | 1 | 8
184 | 1 | 184
Total | 2 | 192

### Octets Transmitted by Chop Size

Chop Size | Count | Octets
4 | 1 | 4
206 | 1 | 206
Total | 2 | 210

### Frames Received by Opcode

Opcode | Count
8 | 1
Total | 1

### Frames Transmitted by Opcode

Opcode | Count
8 | 1
Total | 1

## Wire Log

    000 RX OCTETS: 474554202f72756e436173653f636173653d323430266167656e743d486f726e6265616d20485454502f312e310d0a486f73

                   743a206c6f63616c686f73743a39 ...

    001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

                   5465737453756974652f302e382e ...

    002 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

                   0x03ee

    003 TX OCTETS: 880203ee

    004 FAIL CONNECTION AFTER 1.000000 sec

    005 RX OCTETS: 8882bbfc15f8b812

    006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=6262666331356638

                   0x03ee

    007 TCP DROPPED BY ME