WebSocket++/0.5.1-permessagedeflate - Case 4.1.3 : Pass - 1 ms @ 2015-02-27T15:41:59.277Z
Case Description
Send small text message, then send frame with reserved non-control Opcode = 5, 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 / HTTP/1.1 User-Agent: AutobahnTestSuite/0.7.1-0.10.0 Host: 127.0.0.1:9002 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: vyUvi9+wKzVcwR5CAFvPhg== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: upgrade Sec-WebSocket-Accept: Lhdw4L4BPo/v9njwtE/JUf7rDfE= Server: WebSocketpp/0.5.1-permessagedeflate Upgrade: websocket
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 WebSockets 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 | 1002 | The close code the peer sent me in close frame (if any). |
remoteCloseReason | invalid opcode | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
33 | 1 | 33 |
174 | 1 | 174 |
Total | 2 | 207 |
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 |
5 | 1 |
8 | 1 |
9 | 1 |
Total | 4 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e
312d302e31302e300d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2075706772
6164650d0a5365632d576562536f ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=0c9c2218, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
003 TX OCTETS: 818d0c9c221844f94e7463b0026f63ee4e7c2d
004 TX FRAME : OPCODE=5, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=570c4cdc, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
005 TX OCTETS: 8580570c4cdc
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=ca65b430, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 8980ca65b430
008 FAIL CONNECTION AFTER 1.000000 sec
009 RX OCTETS: 810d48656c6c6f2c20776f726c6421881003ea696e76616c6964206f70636f6465
010 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASKED=False, MASK=None
Hello, world!
011 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=16, MASKED=False, MASK=None
0x03ea696e76616c6964206f70636f6465
012 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=f610d9e0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
013 TX OCTETS: 8882f610d9e0f5f8
014 TCP DROPPED BY PEER