websock secure server - Case 3.2 : Pass - 1 ms @ 2024-04-24T05:20:12.662Z
Case Description
Send small text message, then send again with RSV = 2, then send Ping.
Case Expectation
Echo for first message is received, but then connection is failed immediately, since RSV must be 0, when no extension defining RSV meaning has been negotiated. The Pong is not received.
Case Outcome
Actual events match at least one expected.
Expected:
{'NON-STRICT': [], 'OK': [('message', u'Hello, world!', False)]}
Observed:
[('message', u'Hello, world!', False)]
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: CfDLHuKzapvE4PPXau7vBQ== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Date: Wed, 24 Apr 2024 05:20:12 GMT Upgrade: websocket Connection: Upgrade Sec-Websocket-Accept: QVANxnuvp2YdhRsYY67lYj8uosw=
| 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 |
| 15 | 1 | 15 |
| 166 | 1 | 166 |
| Total | 2 | 181 |
| Chop Size | Count | Octets |
| 6 | 1 | 6 |
| 19 | 2 | 38 |
| 243 | 1 | 243 |
| Total | 4 | 287 |
| Opcode | Count |
| 1 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 2 |
| 9 | 1 |
| Total | 3 |
000 TX OCTETS: 474554202f77737320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f30
2e382e322d302e31302e390d0a48 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205765642c203234204170
7220323032342030353a32303a31 ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=8f0be44b, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
003 TX OCTETS: 818d8f0be44bc76e8827e027c43ce079882fae
004 TX FRAME : OPCODE=1, FIN=True, RSV=2, PAYLOAD-LEN=13, MASK=745c1b4e, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
005 TX OCTETS: a18d745c1b4e3c3977221b703b391b2e772a55
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=03919011, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 898003919011
008 FAIL CONNECTION AFTER 1.000000 sec
009 RX OCTETS: 810d48656c6c6f2c20776f726c6421
010 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASKED=False, MASK=None
Hello, world!
011 TCP DROPPED BY PEER