tokio-websockets - Case 6.4.2 : Pass - 1002 ms @ 2024-11-15T23:18:03.726Z
Case Description
Same as Case 6.4.1, but in 2nd frame, we send only up to and including the octet making the complete payload invalid.
MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5f4
PART2 = 90
PART3 = 8080656469746564
Case Expectation
The first frame is accepted, we expect to timeout on the first wait. The 2nd frame 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')]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=75&agent=tokio-websockets HTTP/1.1 Host: localhost:9001 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: eljz+T2srpAzBWkB69oTqw== 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: oxSbmkS5B9vqvF/YUFSIyN4y/E4=
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 |
191 | 1 | 191 |
Total | 1 | 191 |
Chop Size | Count | Octets |
3 | 1 | 3 |
14 | 1 | 14 |
206 | 1 | 206 |
Total | 3 | 223 |
Opcode | Count |
Total | 0 |
Opcode | Count |
0 | 1 |
1 | 1 |
Total | 2 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3735266167656e743d746f6b696f2d776562736f636b65747320485454502f31
2e310d0a486f73743a206c6f6361 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=12, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0xcebae1bdb9cf83cebcceb5f4
003 TX OCTETS: 010ccebae1bdb9cf83cebcceb5f4
004 DELAY 1.000000 sec for TAG A
005 DELAY TIMEOUT on TAG A
006 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=1, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x90
007 TX OCTETS: 000190
008 DELAY 1.000000 sec for TAG B
009 TCP DROPPED BY PEER