websock-secure-client - Case 2.9 : Pass - 1 ms @ 2024-11-28T05:30:26.039Z
Case Description
Send unsolicited pong with payload. Send ping with payload. Verify pong for ping is received.
Case Expectation
Nothing in reply to own Pong, but Pong with payload echo'ed in reply to Ping. Clean close with normal code.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': [('pong', u'ping payload')]}
Observed:
[('pong', u'ping payload')]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=25&agent=websock-secure-client HTTP/1.1 Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=15 Upgrade: websocket Host: 127.0.0.1:9002 Connection: Upgrade Sec-Websocket-Version: 13 Sec-Websocket-Key: VFF9tWyU5kZYYAvHMNfTJw== Cache-Control: no-cache
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: NzorcmX3mOBW3KevCLpTSAmq6AU=
| 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 | 1000 | The close code I sent in close frame (if any). |
| localCloseReason | None | The close reason I sent in close frame (if any). |
| remoteCloseCode | 1000 | 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 |
| 8 | 1 | 8 |
| 18 | 1 | 18 |
| 294 | 1 | 294 |
| Total | 3 | 320 |
| Chop Size | Count | Octets |
| 4 | 1 | 4 |
| 14 | 1 | 14 |
| 26 | 1 | 26 |
| 206 | 1 | 206 |
| Total | 4 | 250 |
| Opcode | Count |
| 8 | 1 |
| 10 | 1 |
| Total | 2 |
| Opcode | Count |
| 8 | 1 |
| 9 | 1 |
| 10 | 1 |
| Total | 3 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3235266167656e743d776562736f636b2d7365637572652d636c69656e742048
5454502f312e310d0a5365632d57 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=10, FIN=True, RSV=0, PAYLOAD-LEN=24, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
unsolicited pong payload
003 TX OCTETS: 8a18756e736f6c69636974656420706f6e67207061796c6f6164
004 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
ping payload
005 TX OCTETS: 890c70696e67207061796c6f6164
006 CLOSE CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 8a8c6a2853ef1a413d884a5832960647328b
008 RX FRAME : OPCODE=10, FIN=True, RSV=0, PAYLOAD-LEN=12, MASKED=True, MASK=3661323835336566
ping payload
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
010 TX OCTETS: 880203e8
011 RX OCTETS: 88826bd29fb9683a
012 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=3662643239666239
0x03e8
013 TCP DROPPED BY ME