Hornbeam - Case 6.4.3 : Non-Strict - 2003 ms @ 2023-08-11T05:15:14.054Z
Case Description
Same as Case 6.4.1, but we send message not in 3 frames, but in 3 chops of the same message frame.
MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5
PART2 = f4908080
PART3 = 656469746564
Case Expectation
The first chop is accepted, we expect to timeout on the first wait. The 2nd chop should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': [('timeout', 'A')], 'NON-STRICT': [('timeout', 'A'), ('timeout', 'B')]}
Observed:
[('timeout', 'A'), ('timeout', 'B')]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=76&agent=Hornbeam HTTP/1.1 Host: localhost:9001 Upgrade: websocket Connection: upgrade Sec-WebSocket-Key: +iU4rPGz+KULvn0BoACGWQ== 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: /Vzmo5vDNUfx8kCQCAGAOgYzCWc=
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 |
2 | 2 | 4 |
40 | 1 | 40 |
51 | 1 | 51 |
88 | 1 | 88 |
Total | 5 | 183 |
Chop Size | Count | Octets |
2 | 2 | 4 |
4 | 1 | 4 |
6 | 1 | 6 |
11 | 1 | 11 |
206 | 1 | 206 |
Total | 6 | 231 |
Opcode | Count |
Total | 0 |
Opcode | Count |
0 | 1 |
Total | 1 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3736266167656e743d486f726e6265616d20485454502f312e310d0a486f7374
3a206c6f63616c686f73743a3930 ...
001 RX OCTETS: 436f6e6e656374696f6e3a20757067726164650d0a5365632d576562536f636b65742d4b65793a20
002 RX OCTETS: 2b6955347250477a2b4b554c766e30426f41434757513d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031
33
003 RX OCTETS: 0d0a
004 RX OCTETS: 0d0a
005 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
006 TX OCTETS: 0115
007 TX OCTETS: cebae1bdb9cf83cebcceb5
008 DELAY 1.000000 sec for TAG A
009 DELAY TIMEOUT on TAG A
010 TX OCTETS: f4908080
011 DELAY 1.000000 sec for TAG B
012 DELAY TIMEOUT on TAG B
013 TX OCTETS: 656469746564
014 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
015 TX OCTETS: 8000
016 FAIL CONNECTION AFTER 1.000000 sec
017 TCP DROPPED BY PEER