WebSocket++/0.5.1-permessagedeflate - Case 5.18 : Pass - 1 ms @ 2015-02-27T15:41:59.357Z
Case Description
Send text Message fragmented into 2 fragments, with both frame opcodes set to text, sent in one chop.
Case Expectation
The connection is failed immediately, since all data frames after the initial data frame must have opcode 0.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
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: vlxYYgZqNuoaaPo8pmQtDg== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: upgrade Sec-WebSocket-Accept: WP8xnHmuBENeiuaZse/E5d1DLD4= 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 message continuation | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 32 | 1 | 32 |
| 174 | 1 | 174 |
| Total | 2 | 206 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 15 | 2 | 30 |
| 240 | 1 | 240 |
| Total | 4 | 278 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 2 |
| 8 | 1 |
| Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e
312d302e31302e300d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2075706772
6164650d0a5365632d576562536f ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=1a0bd59d, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
003 TX OCTETS: 01891a0bd59d7c79b4fa776ebbe92b
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=436cdbb4, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
005 TX OCTETS: 8189436cdbb4251ebad32e09b5c071
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 881e03ea496e76616c6964206d65737361676520636f6e74696e756174696f6e
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=30, MASKED=False, MASK=None
0x03ea496e76616c6964206d65737361676520636f6e74696e756174696f6e
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=d91dee08, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
010 TX OCTETS: 8882d91dee08daf5
011 TCP DROPPED BY PEER