WebSocket++ 0.2.0dev - Case 5.2 : Pass - 1 ms @ 2012-10-12T12:13:31Z
Case Description
Send Pong 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.5.2-0.5.8 Host: localhost:9002 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Key: L7KtfLhi93oJDslZCaikOw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: Upgrade Sec-WebSocket-Accept: 7/TdcFldF7OZV4bmI1CQTRy4Gos= Server: WebSocket++/0.2.0dev 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 | Fragmented control message | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 30 | 1 | 30 |
| 159 | 1 | 159 |
| Total | 2 | 189 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 15 | 2 | 30 |
| 196 | 1 | 196 |
| Total | 4 | 234 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 0 | 1 |
| 8 | 1 |
| 10 | 1 |
| Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
322d302e352e380d0a486f73743a206c6f63616c686f73743a393030320d0a557067726164653a20576562536f636b65740d
0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a204c374b74664c686939
336f4a44736c5a4361696b4f773d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772
6164650d0a5365632d576562536f636b65742d4163636570743a20372f546463466c6446374f5a5634626d49314351545279
34476f733d0d0a5365727665723a20576562536f636b65742b2b2f302e322e306465760d0a557067726164653a2077656273
6f636b65740d0a0d0a
002 TX FRAME : OPCODE=10, FIN=False, RSV=0, MASK=07ec5f17, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
003 TX OCTETS: 0a8907ec5f17619e3e706a89316336
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, MASK=3efa13c0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
005 TX OCTETS: 80893efa13c0588872a7539f7db40c
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 881c03ea467261676d656e74656420636f6e74726f6c206d657373616765
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
źFragmented control message
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=9f838d22, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
č
010 TX OCTETS: 88829f838d229c6b
011 TCP DROPPED BY PEER