WebSocket /0.2.0-dev - Case 7.9.1 : Pass - 1 ms @ 2012-10-12T12:21:07Z
Case Description
Send close with invalid close code 0
Case Expectation
Clean close with protocol error code or drop TCP
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=226&agent=WebSocket++/0.2.0-dev HTTP/1.1 Connection: Upgrade Host: localhost:9001 Sec-WebSocket-Key: 76EoTP/L9sjilVdW6O8+oQ== 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: 6V4tlkWupwEwRDMELJzzdeL0tZs=
| Key | Value | Description |
| isServer | True | True, iff I (the fuzzer) am a server, and the peer is a client. |
| closedByMe | True | 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 | 0 | 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 | Close code is not allowed on the wire. | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 46 | 1 | 46 |
| 231 | 1 | 231 |
| Total | 2 | 277 |
| Chop Size | Count | Octets |
| 4 | 1 | 4 |
| 168 | 1 | 168 |
| Total | 2 | 172 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
000 RX OCTETS: 474554202f72756e436173653f636173653d323236266167656e743d576562536f636b65742b2b2f302e322e302d64657620
485454502f312e310d0a436f6e6e656374696f6e3a20557067726164650d0a486f73743a206c6f63616c686f73743a393030
310d0a5365632d576562536f636b65742d4b65793a203736456f54502f4c39736a696c566457364f382b6f513d3d0d0a5365
632d576562536f636b65742d56657273696f6e3a2031330d0a557067726164653a20776562736f636b65740d0a557365722d
4167656e743a20576562536f636b65742b2b2f302e322e306465760d0a0d0a
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e352e322d302e352e380d0a557067726164653a20576562536f636b65740d0a436f6e6e656374
696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a20365634746c6b5775707745775244
4d454c4a7a7a64654c30745a733d0d0a0d0a
002 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
003 TX OCTETS: 88020000
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 88a8729f161a717555761dec733a11f0727f52f6653a1cf0623a13f37a7505fa723a1df1366e1afa366d1bed7334
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=True, MASK=3732396631363161
ęClose code is not allowed on the wire.
007 TCP DROPPED BY ME