websock secure server - Case 6.3.1 : Pass - 0 ms @ 2024-04-24T05:20:15.041Z
Case Description
Send invalid UTF-8 text message unfragmented.
MESSAGE:
cebae1bdb9cf83cebcceb5eda080656469746564
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /wss HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: 127.0.0.1:8889 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: t8/h2oyY/IxI6eCI3xwJGw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Date: Wed, 24 Apr 2024 05:20:15 GMT Upgrade: websocket Connection: Upgrade Sec-Websocket-Accept: THeyxOiKxTlrQuKD3ZPBeayJlj4=
| 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 |
| 26 | 1 | 26 |
| 243 | 1 | 243 |
| Total | 2 | 269 |
| Opcode | Count |
| Total | 0 |
| Opcode | Count |
| 1 | 1 |
| Total | 1 |
000 TX OCTETS: 474554202f77737320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f30
2e382e322d302e31302e390d0a48 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205765642c203234204170
7220323032342030353a32303a31 ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=20, MASK=56969bd2, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Îºá½¹ÏƒÎ¼Îµí €edited
003 TX OCTETS: 819456969bd2982c7a6fef59181cea582e3ff616feb63fe2feb6
004 FAIL CONNECTION AFTER 1.000000 sec
005 TCP DROPPED BY PEER