Chrome/22.0.1229.94 - Case 7.9.8 : Pass - 1 ms @ 2012-10-12T12:34:35Z
Case Description
Send close with invalid close code 1014
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=233&agent=Chrome/22.0.1229.94 HTTP/1.1 Upgrade: websocket Connection: Upgrade Host: localhost:9001 Origin: http://localhost:8080 Sec-WebSocket-Key: RCH4hv+xivgTYANMQygudA== Sec-WebSocket-Version: 13 Sec-WebSocket-Extensions: x-webkit-deflate-frame
HTTP/1.1 101 Switching Protocols Server: AutobahnTestSuite/0.5.2-0.5.8 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: V81sFNYOEo5FFGShOq0AsIoY7Uw=
| 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 | 1014 | The close code I sent in close frame (if any). |
| localCloseReason | None | The close reason I sent in close frame (if any). |
| remoteCloseCode | None | The close code the peer sent me in close frame (if any). |
| remoteCloseReason | None | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 6 | 1 | 6 |
| 276 | 1 | 276 |
| Total | 2 | 282 |
| 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: 474554202f72756e436173653f636173653d323333266167656e743d4368726f6d652f32322e302e313232392e3934204854
54502f312e310d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a48
6f73743a206c6f63616c686f73743a393030310d0a4f726967696e3a20687474703a2f2f6c6f63616c686f73743a38303830
0d0a5365632d576562536f636b65742d4b65793a205243483468762b786976675459414e4d5179677564413d3d0d0a536563
2d576562536f636b65742d56657273696f6e3a2031330d0a5365632d576562536f636b65742d457874656e73696f6e733a20
782d7765626b ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e352e322d302e352e380d0a557067726164653a20576562536f636b65740d0a436f6e6e656374
696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a2056383173464e594f456f35464647
53684f71304173496f593755773d0d0a0d0a
002 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
ö
003 TX OCTETS: 880203f6
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 88801ee4f1f9
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=True, MASK=3165653466316639
007 TCP DROPPED BY ME