websock server - Case 6.4.2 : Non-Strict - 2001 ms @ 2024-04-24T05:20:16.417Z
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:
{'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: jtfYtJyA+2RTU1TjXrLEUQ== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Date: Wed, 24 Apr 2024 05:20:16 GMT Upgrade: websocket Connection: Upgrade Sec-Websocket-Accept: vpPHrGLAJJhhro7rD04hDpUdfjY=
| 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 |
| 7 | 1 | 7 |
| 14 | 1 | 14 |
| 18 | 1 | 18 |
| 242 | 1 | 242 |
| Total | 4 | 281 |
| Opcode | Count |
| Total | 0 |
| Opcode | Count |
| 0 | 2 |
| 1 | 1 |
| Total | 3 |
000 TX OCTETS: 474554202f777320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e
382e322d302e31302e390d0a486f ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205765642c203234204170
7220323032342030353a32303a31 ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=12, MASK=dd06b840, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0xcebae1bdb9cf83cebcceb5f4
003 TX OCTETS: 018cdd06b84013bc59fd64c93b8e61c80db4
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=b9eb7635, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x90
007 TX OCTETS: 0081b9eb763529
008 DELAY 1.000000 sec for TAG B
009 DELAY TIMEOUT on TAG B
010 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=8, MASK=8a93a818, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x8080656469746564
011 TX OCTETS: 80888a93a8180a13cd7ce3e7cd7c
012 FAIL CONNECTION AFTER 1.000000 sec
013 TCP DROPPED BY PEER