websock server - Case 4.2.4 : Pass - 0 ms @ 2024-04-24T05:20:12.222Z
Case Description
Send small text message, then send frame with reserved control Opcode = 14 and non-empty payload, then send Ping.
Case Expectation
Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A 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 /ws HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: 127.0.0.1:8888 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: nZHcCxn2YBHP7/0QJtrQUA== 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: YkYinGKF7D+y0uMDH9yx7nASPVE=
| 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 |
| 242 | 1 | 242 |
| Total | 4 | 286 |
| Opcode | Count |
| 1 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 1 |
| 9 | 1 |
| 14 | 1 |
| Total | 3 |
000 TX OCTETS: 474554202f777320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e
382e322d302e31302e390d0a486f ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205765642c203234204170
7220323032342030353a32303a31 ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=659ce2f4, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
003 TX OCTETS: 818d659ce2f42df98e980ab0c2830aee8e9044
004 TX FRAME : OPCODE=14, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=c64cab1b, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
005 TX OCTETS: 8e8dc64cab1b8e29c777a9608b6ca93ec77fe7
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=befafea9, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 8980befafea9
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