async-client - Case 3.6 : Pass - 4 ms @ 2023-02-24T01:34:05.242Z
Case Description
Send Ping with RSV = 6.
Case Expectation
The connection is failed immediately, since RSV must be 0.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
The close code should have been 1002 or empty (WRONG CODE)
GET /runCase?case=33&agent=async-client HTTP/1.1 Host: localhost:9002 Upgrade: websocket Connection: Upgrade Sec-Websocket-Key: JBjqkvnQSg+2luMsWuWe5A== Sec-WebSocket-Version: 13
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: uRF/DG9ZgHrTdrMzliKWXHKF0WI=
| Key | Value | Description |
| isServer | True | 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 | 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 | 1000 | The close code I sent in close frame (if any). |
| localCloseReason | None | The close reason I sent in close frame (if any). |
| remoteCloseCode | 1008 | The close code the peer sent me in close frame (if any). |
| remoteCloseReason | invalid leading bits 1110 | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 187 | 1 | 187 |
| 1122 | 1 | 1122 |
| Total | 2 | 1309 |
| Chop Size | Count | Octets |
| 4 | 1 | 4 |
| 15 | 1 | 15 |
| 206 | 1 | 206 |
| Total | 3 | 225 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 2 | 1 |
| 8 | 1 |
| Total | 2 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3333266167656e743d6173796e632d636c69656e7420485454502f312e310d0a
486f73743a206c6f63616c686f73 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=2, FIN=True, RSV=6, PAYLOAD-LEN=13, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
003 TX OCTETS: e20d48656c6c6f2c20776f726c6421
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 889bcf19239ecce94af0b9784ff7ab394ffbae7d4af0a83941f7bb6a03affe2813889b09aba29a0a5bcbf47fcacef36d8bce
ff68cfcbf46e8bc0f37dd882ab38 ...
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=27, MASKED=True, MASK=6366313932333965
0x03f0696e76616c6964206c656164696e6720626974732031313130
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
008 TX OCTETS: 880203e8
009 TCP DROPPED BY ME