WebSocket-Node 1.0.27 - Case 6.12.8 : Pass - 2 ms @ 2020-08-28T14:51:22.870Z
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0x808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9fa0a1a2a3a4a5a6a7a8a9aaabacadaeafb0b1b2b3b4b5b6b7b8b9babbbcbdbe
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 / HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.1-0.10.9 Host: host.docker.internal:8080 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: vVq7skr5PPgDVAqUUHUdXg== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: aPZrbNw7xU+erRFwVPCPgzWOQyc=
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 | True | True, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility). |
wasNotCleanReason | None | 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 | 1000 | The close code I sent in close frame (if any). |
localCloseReason | None | The close reason I sent in close frame (if any). |
remoteCloseCode | 1007 | The close code the peer sent me in close frame (if any). |
remoteCloseReason | Invalid UTF-8 Data Received | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
31 | 1 | 31 |
129 | 1 | 129 |
Total | 2 | 160 |
Chop Size | Count | Octets |
8 | 1 | 8 |
69 | 1 | 69 |
251 | 1 | 251 |
Total | 3 | 328 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
1 | 1 |
8 | 1 |
Total | 2 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
312d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=63, MASK=295b969a, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9fa0a1a2a3a4a5a6a7a8a9aaabacadaeafb0
b1b2b3b4b5b6b7b8b9babbbcbdbe ...
003 TX OCTETS: 81bf295b969aa9da1419adde101da1d21c11a5d61815b9ca0409bdce000db1c20c01b5c6080589fa34398dfe303d81f23c31
85f6383599ea24299dee202d91e2 ...
004 FAIL CONNECTION AFTER 0.500000 sec
005 RX OCTETS: 881d03ef496e76616c6964205554462d382044617461205265636569766564
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=29, MASKED=False, MASK=None
0x03ef496e76616c6964205554462d382044617461205265636569766564
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=ebd2faeb, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
008 TX OCTETS: 8882ebd2faebe83a
009 TCP DROPPED BY PEER