tokio-websockets - Case 4.2.5 : Pass - 4 ms @ 2024-11-15T23:18:00.583Z
Case Description
Send small text message, then send frame with reserved control Opcode = 15 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:
{'OK': [('message', u'Hello, world!', False)], 'NON-STRICT': []}
Observed:
[('message', u'Hello, world!', False)]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=44&agent=tokio-websockets HTTP/1.1 Host: localhost:9001 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: OpLqNBgsTmPLOJ4EFwb9CQ== 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: FQAkMOtOtcClWnuC257MYcG5RQ0=
| 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 | 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 |
| 19 | 1 | 19 |
| 191 | 1 | 191 |
| Total | 2 | 210 |
| Chop Size | Count | Octets |
| 1 | 18 | 18 |
| 206 | 1 | 206 |
| Total | 19 | 224 |
| Opcode | Count |
| 1 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 1 |
| 9 | 1 |
| 15 | 1 |
| Total | 3 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3434266167656e743d746f6b696f2d776562736f636b65747320485454502f31
2e310d0a486f73743a206c6f6361 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
Hello, world!
003 TX OCTETS: 81
004 TX FRAME : OPCODE=15, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
Hello, world!
005 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
006 FAIL CONNECTION AFTER 1.000000 sec
007 TX OCTETS: 0d
008 TX OCTETS: 48
009 TX OCTETS: 65
010 TX OCTETS: 6c
011 TX OCTETS: 6c
012 TX OCTETS: 6f
013 TX OCTETS: 2c
014 TX OCTETS: 20
015 TX OCTETS: 77
016 TX OCTETS: 6f
017 TX OCTETS: 72
018 TX OCTETS: 6c
019 TX OCTETS: 64
020 TX OCTETS: 21
021 TX OCTETS: 8f
022 RX OCTETS: 818dcf53228587364ee9a07f02f2a0214ee1ee
023 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASKED=True, MASK=6366353332323835
Hello, world!
024 TX OCTETS: 0d
025 TX OCTETS: 48
026 TCP DROPPED BY PEER