rust-websocket - Case 4.2.4 : Pass - 2 ms @ 2018-10-31T02:16:57.205Z
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 /runCase?case=43&agent=rust-websocket HTTP/1.1 Host: 127.0.0.1:9001 Connection: Upgrade Upgrade: websocket Sec-WebSocket-Version: 13 Sec-WebSocket-Key: 5xPbeeAKJSSF5zLAkDA46A==
HTTP/1.1 101 Switching Protocols Server: AutobahnTestSuite/0.8.0-0.10.9 X-Powered-By: AutobahnPython/0.10.9 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: vCNCoTC2Q6YUKzqMBinwuRjAnTE=
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 | 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 |
25 | 1 | 25 |
189 | 1 | 189 |
Total | 2 | 214 |
Chop Size | Count | Octets |
2 | 1 | 2 |
4 | 1 | 4 |
15 | 2 | 30 |
206 | 1 | 206 |
Total | 5 | 242 |
Opcode | Count |
1 | 1 |
8 | 1 |
Total | 2 |
Opcode | Count |
1 | 1 |
8 | 1 |
9 | 1 |
14 | 1 |
Total | 4 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3433266167656e743d727573742d776562736f636b657420485454502f312e31
0d0a486f73743a203132372e302e ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
003 TX OCTETS: 810d48656c6c6f2c20776f726c6421
004 TX FRAME : OPCODE=14, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
005 TX OCTETS: 8e0d48656c6c6f2c20776f726c6421
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 8900
008 FAIL CONNECTION AFTER 1.000000 sec
009 RX OCTETS: 818d8c6b80bfc40eecd3e347a0c8e319ecdbad88804e4efad1
010 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASKED=True, MASK=3863366238306266
Hello, world!
011 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=True, MASK=3465346566616431
012 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
013 TX OCTETS: 880203e8
014 TCP DROPPED BY ME