Chrome/22.0.1229.94 - Case 5.18 : Pass - 1 ms @ 2012-10-12T12:34:24Z
Case Description
Send text Message fragmented into 2 fragments, with both frame opcodes set to text, sent in one chop.
Case Expectation
The connection is failed immediately, since all data frames after the initial data frame must have opcode 0.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=62&agent=Chrome/22.0.1229.94 HTTP/1.1 Upgrade: websocket Connection: Upgrade Host: localhost:9001 Origin: http://localhost:8080 Sec-WebSocket-Key: CefYknT+KXVRNZCl8N5yIg== 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: AlN8ref04GygvdpjhT7HAje0rv4=
| 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 | False | True, iff I dropped the TCP connection. |
| wasClean | False | True, iff full WebSockets closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility). |
| wasNotCleanReason | peer dropped the TCP connection without previous WebSocket closing handshake | 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 | None | 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 |
| 275 | 1 | 275 |
| Total | 1 | 275 |
| Chop Size | Count | Octets |
| 11 | 2 | 22 |
| 168 | 1 | 168 |
| Total | 3 | 190 |
| Opcode | Count |
| Total | 0 |
| Opcode | Count |
| 1 | 2 |
| Total | 2 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3632266167656e743d4368726f6d652f32322e302e313232392e393420485454
502f312e310d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a486f
73743a206c6f63616c686f73743a393030310d0a4f726967696e3a20687474703a2f2f6c6f63616c686f73743a383038300d
0a5365632d576562536f636b65742d4b65793a20436566596b6e542b4b5856524e5a436c384e357949673d3d0d0a5365632d
576562536f636b65742d56657273696f6e3a2031330d0a5365632d576562536f636b65742d457874656e73696f6e733a2078
2d7765626b69 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e352e322d302e352e380d0a557067726164653a20576562536f636b65740d0a436f6e6e656374
696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a20416c4e3872656630344779677664
706a68543748416a65307276343d0d0a0d0a
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
003 TX OCTETS: 0109667261676d656e7431
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
005 TX OCTETS: 8109667261676d656e7432
006 FAIL CONNECTION AFTER 1.000000 sec
007 TCP DROPPED BY PEER