WebSocket++/0.5.1-permessagedeflate - Case 5.1 : Pass - 1 ms @ 2015-02-27T15:41:59.298Z
Case Description
Send Ping fragmented into 2 fragments.
Case Expectation
Connection is failed immediately, since control message MUST NOT be fragmented.
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: DsSIZ+81rAk/p6Y9wMXGTg== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: upgrade Sec-WebSocket-Accept: nypw+cuJvhJiK/oUIi4U6N3RxmQ= 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 | Control messages cannot be fragmented | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
41 | 1 | 41 |
174 | 1 | 174 |
Total | 2 | 215 |
Chop Size | Count | Octets |
8 | 1 | 8 |
15 | 2 | 30 |
240 | 1 | 240 |
Total | 4 | 278 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
0 | 1 |
8 | 1 |
9 | 1 |
Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e
312d302e31302e300d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2075706772
6164650d0a5365632d576562536f ...
002 TX FRAME : OPCODE=9, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=082bcd02, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
003 TX OCTETS: 0989082bcd026e59ac65654ea37639
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=e42df048, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
005 TX OCTETS: 8089e42df048825f912f89489e3cd6
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 882703ea436f6e74726f6c206d657373616765732063616e6e6f7420626520667261676d656e746564
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=39, MASKED=False, MASK=None
0x03ea436f6e74726f6c206d657373616765732063616e6e6f7420626520667261676d656e746564
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=39111e56, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
010 TX OCTETS: 888239111e563af9
011 TCP DROPPED BY PEER