Hornbeam - Case 5.19 : Fail - 3 ms @ 2023-08-10T21:35:06.307Z
Case Description
A fragmented text message is sent in multiple frames. After
sending the first 2 frames of the text message, a Ping is sent. Then we wait 1s,
then we send 2 more text fragments, another Ping and then the final text fragment.
Everything is legal.
Case Expectation
The peer immediately answers the first Ping before
it has received the last text message fragment. The peer pong's back the Ping's
payload exactly, and echo's the payload of the fragmented message back to us.
Case Outcome
Actual events differ from any expected.
Expected:
{'OK': [('pong', u'pongme 1!'), ('pong', u'pongme 2!'), ('message', u'fragment1fragment2fragment3fragment4fragment5', False)]}
Observed:
[('message', u'fragment1', False)]
Case Closing Behavior
The connection was failed by the wrong endpoint (FAILED)
GET /runCase?case=63&agent=Hornbeam HTTP/1.1 Host: localhost:9001 Upgrade: websocket Connection: upgrade Sec-WebSocket-Key: lE4MKWYqZ/141sAC/vfzFA== 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: E59Rf2hwPndGs41abYrcdguNOUw=
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). |
Chop Size | Count | Octets |
1 | 1 | 1 |
14 | 1 | 14 |
183 | 1 | 183 |
Total | 3 | 198 |
Chop Size | Count | Octets |
11 | 3 | 33 |
206 | 1 | 206 |
Total | 4 | 239 |
Opcode | Count |
1 | 1 |
Total | 1 |
Opcode | Count |
0 | 1 |
1 | 1 |
9 | 1 |
Total | 3 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3633266167656e743d486f726e6265616d20485454502f312e310d0a486f7374
3a206c6f63616c686f73743a3930 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
003 TX OCTETS: 0109667261676d656e7431
004 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
005 TX OCTETS: 0009667261676d656e7432
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
pongme 1!
007 TX OCTETS: 8909706f6e676d65203121
008 DELAY 1.000000 sec for TAG None
009 RX OCTETS: 81
010 RX OCTETS: 8939b2e50c5fc0846b54d78b7808
011 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=9, MASKED=True, MASK=3339623265353063
fragment1
012 TCP DROPPED BY PEER