WebSocketpp/0.5.1-permessagedeflate - Case 5.10 : Pass - 1 ms @ 2015-02-27T15:15:44.329Z
Case Description
Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in per-frame chops.
Case Expectation
The connection is failed immediately, since there is no message to continue.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=54&agent=WebSocketpp/0.5.1-permessagedeflate HTTP/1.1 Connection: Upgrade Host: localhost:9001 Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits Sec-WebSocket-Key: f6ct5iJxbAWN9GpdbuJTvg== Sec-WebSocket-Version: 13 Upgrade: websocket User-Agent: WebSocketpp/0.5.1-permessagedeflate
HTTP/1.1 101 Switching Protocols Server: AutobahnTestSuite/0.7.1-0.10.0 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: X+u2J90ENFGgY07cR5LiM+mviuA=
| 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 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 message continuation | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 36 | 1 | 36 |
| 357 | 1 | 357 |
| Total | 2 | 393 |
| Chop Size | Count | Octets |
| 4 | 1 | 4 |
| 15 | 1 | 15 |
| 26 | 1 | 26 |
| 169 | 1 | 169 |
| Total | 4 | 214 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 0 | 1 |
| 1 | 1 |
| 8 | 1 |
| Total | 3 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3534266167656e743d576562536f636b657470702f302e352e312d7065726d65
73736167656465666c6174652048 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e372e ...
002 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=24, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
non-continuation payload
003 TX OCTETS: 80186e6f6e2d636f6e74696e756174696f6e207061796c6f6164
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
Hello, world!
005 FAIL CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 810d48656c6c6f2c20776f726c6421
007 RX OCTETS: 889e44fa9f4c4710d622329bf32520daf2293789fe2b21dafc232a8ef622319beb252b94
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=30, MASKED=True, MASK=3434666139663463
0x03ea496e76616c6964206d65737361676520636f6e74696e756174696f6e
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
010 TX OCTETS: 880203e8
011 TCP DROPPED BY ME