Hornbeam - Case 6.1.3 : Fail - 3 ms @ 2023-08-10T21:35:06.368Z

Case Description
Send fragmented text message, 3 fragments, first and last of length 0, middle non-empty.

Case Expectation
A message is echo'ed back to us (with payload = payload of middle fragment).

Case Outcome
Actual events differ from any expected.
Expected:
{'OK': [('message', u'middle frame payload', False)]}
Observed:
[('message', u'', False)]

Case Closing Behavior
The connection was failed by the wrong endpoint (FAILED)

## Opening Handshake

    GET /runCase?case=67&agent=Hornbeam HTTP/1.1
    Host: localhost:9001
    Upgrade: websocket
    Connection: upgrade
    Sec-WebSocket-Key: Krod0B+bF/zTtxh2jPdskQ==
    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: bGUD0BEFC6sPV3q2EZDxsHBTY/I=

## Closing Behavior

Key | Value | Description
isServer | True | True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe | False | True, iff I have initiated closing handshake (that is, did send close first).
failedByMe | False | 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 | False | 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 | peer dropped the TCP connection without previous WebSocket closing handshake | 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 | None | The close code I sent in close frame (if any).
localCloseReason | None | The close reason I sent in close frame (if any).
remoteCloseCode | None | 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
1 | 1 | 1
5 | 1 | 5
183 | 1 | 183
Total | 3 | 189

### Octets Transmitted by Chop Size

Chop Size | Count | Octets
2 | 2 | 4
22 | 1 | 22
206 | 1 | 206
Total | 4 | 232

### Frames Received by Opcode

Opcode | Count
1 | 1
Total | 1

### Frames Transmitted by Opcode

Opcode | Count
0 | 2
1 | 1
Total | 3

## Wire Log

    000 RX OCTETS: 474554202f72756e436173653f636173653d3637266167656e743d486f726e6265616d20485454502f312e310d0a486f7374

                   3a206c6f63616c686f73743a3930 ...

    001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

                   5465737453756974652f302e382e ...

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

    003 TX OCTETS: 0100

    004 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=20, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

                   middle frame payload

    005 TX OCTETS: 00146d6964646c65206672616d65207061796c6f6164

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

    007 TX OCTETS: 8000

    008 CLOSE CONNECTION AFTER 1.000000 sec

    009 RX OCTETS: 81

    010 RX OCTETS: 808d280333

    011 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=True, MASK=3864323830333333

    012 TCP DROPPED BY PEER