WebSocket /0.2.0-dev - Case 5.1 : Pass - 1 ms @ 2012-10-12T12:20:59Z
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 /runCase?case=45&agent=WebSocket++/0.2.0-dev HTTP/1.1 Connection: Upgrade Host: localhost:9001 Sec-WebSocket-Key: 2LW413ztga5oK8vPUPZuBA== Sec-WebSocket-Version: 13 Upgrade: websocket User-Agent: WebSocket++/0.2.0dev
HTTP/1.1 101 Switching Protocols Server: AutobahnTestSuite/0.5.2-0.5.8 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: HUc9pA1UXtkDXYK4m6v8cncA3+Y=
| 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 | Fragmented control message | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 34 | 1 | 34 |
| 230 | 1 | 230 |
| Total | 2 | 264 |
| Chop Size | Count | Octets |
| 4 | 1 | 4 |
| 11 | 2 | 22 |
| 168 | 1 | 168 |
| Total | 4 | 194 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 0 | 1 |
| 8 | 1 |
| 9 | 1 |
| Total | 3 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3435266167656e743d576562536f636b65742b2b2f302e322e302d6465762048
5454502f312e310d0a436f6e6e656374696f6e3a20557067726164650d0a486f73743a206c6f63616c686f73743a39303031
0d0a5365632d576562536f636b65742d4b65793a20324c573431337a746761356f4b38765055505a7542413d3d0d0a536563
2d576562536f636b65742d56657273696f6e3a2031330d0a557067726164653a20776562736f636b65740d0a557365722d41
67656e743a20576562536f636b65742b2b2f302e322e306465760d0a0d0a
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e352e322d302e352e380d0a557067726164653a20576562536f636b65740d0a436f6e6e656374
696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a20485563397041315558746b445859
4b346d367638636e6341332b593d0d0a0d0a
002 TX FRAME : OPCODE=9, FIN=False, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
003 TX OCTETS: 0909667261676d656e7431
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
005 TX OCTETS: 8009667261676d656e7432
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 889c6deefc256e04ba570c899140039a99414d8d934b199c93494d8399561e8f9b40
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=True, MASK=3664656566633235
źFragmented control message
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
č
010 TX OCTETS: 880203e8
011 TCP DROPPED BY ME