WebSocket++ 0.2.0dev - Case 7.9.5 : Pass - 1 ms @ 2012-10-12T12:13:38Z
Case Description
Send close with invalid close code 1006
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 / HTTP/1.1 User-Agent: AutobahnTestSuite/0.5.2-0.5.8 Host: localhost:9002 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Key: EAjBhgOqj6C96/Esdh75rQ== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: Upgrade Sec-WebSocket-Accept: aAti1AuKNIOf7KBnaDeYcIDDl8s= 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 | 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 | 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 | 1006 | 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 |
| 42 | 1 | 42 |
| 159 | 1 | 159 |
| Total | 2 | 201 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 196 | 1 | 196 |
| Total | 2 | 204 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
322d302e352e380d0a486f73743a206c6f63616c686f73743a393030320d0a557067726164653a20576562536f636b65740d
0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a2045416a4268674f716a
364339362f45736468373572513d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772
6164650d0a5365632d576562536f636b65742d4163636570743a20614174693141754b4e494f66374b426e61446559634944
446c38733d0d0a5365727665723a20576562536f636b65742b2b2f302e322e306465760d0a557067726164653a2077656273
6f636b65740d0a0d0a
002 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=af6c1c3a, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
î
003 TX OCTETS: 8882af6c1c3aac82
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 882803ea436c6f736520636f6465206973206e6f7420616c6c6f776564206f6e2074686520776972652e
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
êClose code is not allowed on the wire.
007 TCP DROPPED BY PEER