WSServer (HTTPS) - Case 4.2.3 : Pass - 2 ms @ 2020-12-10T23:53:44.083Z
Case Description
Send small text message, then send frame with reserved control Opcode = 13, 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
The close code should have been 1002 or empty (WRONG CODE)
GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.1-0.10.9 Host: 127.0.0.1:9011 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: v+SfHK7njnYjdwq31Xu/HQ== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Sec-Websocket-Accept: q3j+PUP5PKTN0aqAY14bfEUL7Kg= Upgrade: websocket Connection: Upgrade Server: WSServer/v2.0.7
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 | 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 | 1003 | The close code the peer sent me in close frame (if any). |
remoteCloseReason | Unsupported data type | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
15 | 1 | 15 |
25 | 1 | 25 |
154 | 1 | 154 |
Total | 3 | 194 |
Chop Size | Count | Octets |
6 | 2 | 12 |
8 | 1 | 8 |
19 | 1 | 19 |
240 | 1 | 240 |
Total | 5 | 279 |
Opcode | Count |
1 | 1 |
8 | 1 |
Total | 2 |
Opcode | Count |
1 | 1 |
8 | 1 |
9 | 1 |
13 | 1 |
Total | 4 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
312d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365632d576562736f636b65742d4163
636570743a2071336a2b50555035 ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=5093848f, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
003 TX OCTETS: 818d5093848f18f6e8e33fbfa4f83fe1e8eb71
004 TX FRAME : OPCODE=13, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=4d12d5c9, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
005 TX OCTETS: 8d804d12d5c9
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=31a4b49c, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 898031a4b49c
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 RX OCTETS: 881703eb556e737570706f7274656420646174612074797065
012 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=23, MASKED=False, MASK=None
0x03eb556e737570706f7274656420646174612074797065
013 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=92e842b6, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
014 TX OCTETS: 888292e842b69100
015 TCP DROPPED BY PEER