websock server - Case 6.4.3 : Non-Strict - 2001 ms @ 2024-11-28T05:30:56.408Z
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:
{'NON-STRICT': [('timeout', 'A'), ('timeout', 'B')], 'OK': [('timeout', 'A')]}
Observed:
[('timeout', 'A'), ('timeout', 'B')]
Case Closing Behavior
Connection was properly closed (OK)
GET /ws HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: 127.0.0.1:8888 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: 7QkTR+6ZdewNUt3smfsQwA== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Date: Thu, 28 Nov 2024 05:30:56 GMT Upgrade: websocket Connection: Upgrade Sec-Websocket-Accept: 40JNaQj70wz9cHLd+7g2AOvL2MU=
Key | Value | Description |
isServer | False | 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 |
166 | 1 | 166 |
Total | 1 | 166 |
Chop Size | Count | Octets |
4 | 1 | 4 |
6 | 3 | 18 |
11 | 1 | 11 |
242 | 1 | 242 |
Total | 6 | 275 |
Opcode | Count |
Total | 0 |
Opcode | Count |
0 | 1 |
Total | 1 |
000 TX OCTETS: 474554202f777320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e
382e322d302e31302e390d0a486f ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205468752c203238204e6f
7620323032342030353a33303a35 ...
002 TX OCTETS: 019597445a3d
003 TX OCTETS: 59febb802e8bd9f32b8aef
004 DELAY 1.000000 sec for TAG A
005 DELAY TIMEOUT on TAG A
006 TX OCTETS: c907c4da
007 DELAY 1.000000 sec for TAG B
008 DELAY TIMEOUT on TAG B
009 TX OCTETS: 58f32d2e58f3
010 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=6f22ef4d, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
011 TX OCTETS: 80806f22ef4d
012 FAIL CONNECTION AFTER 1.000000 sec
013 TCP DROPPED BY PEER