wtx - Case 7.9.9 : Pass - 1 ms @ 2023-09-27T21:03:48.310Z
Case Description
Send close with invalid close code 2999
Case Expectation
Clean close with protocol error code or drop TCP
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=244&agent=wtx HTTP/1.1 Connection: Upgrade Host: 127.0.0.1:9080 Sec-WebSocket-Key: A3NrEB3KLDKsOqucbwDClA== Sec-WebSocket-Version: 13 Upgrade: websocket Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=12; server_max_window_bits=12; client_no_context_takeover; server_no_context_takeover
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: LvLsQU7+LpowFEomP9Ys4OnoknE=
Key | Value | Description |
isServer | True | True, iff I (the fuzzer) am a server, and the peer is a client. |
closedByMe | True | 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 | True | 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 | 2999 | The close code I sent in close frame (if any). |
localCloseReason | None | The close reason I sent in close frame (if any). |
remoteCloseCode | 1002 | 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 |
14 | 1 | 14 |
335 | 1 | 335 |
Total | 2 | 349 |
Chop Size | Count | Octets |
4 | 1 | 4 |
206 | 1 | 206 |
Total | 2 | 210 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
8 | 1 |
Total | 1 |
000 RX OCTETS: 474554202f72756e436173653f636173653d323434266167656e743d77747820485454502f312e310d0a436f6e6e65637469
6f6e3a20557067726164650d0a48 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x0bb7
003 TX OCTETS: 88020bb7
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 8882d06201c4d38888809b025e7d
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=6430363230316334
0x03ea
007 TCP DROPPED BY ME