AutobahnServer - Case 6.4.3 : Pass - 1001 ms @ 2013-03-03T15:37:43Z
Case Description
Same as Case 6.4.1, but we send message not in 3 frames, but in 3 chops of the same message frame.
MESSAGE PARTS:
PART1 = κόσμε (cebae1bdb9cf83cebcceb5)
PART2 = (f4908080)
PART3 = edited (656469746564)
Case Expectation
The first chop is accepted, we expect to timeout on the first wait. The 2nd chop should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.
Case Outcome
Actual events match at least one expected.
Expected:
{'NON-STRICT': [('timeout', 'A'), ('timeout', 'B')], 'OK': [('timeout', 'A')]}
Observed:
[('timeout', 'A')]
Case Closing Behavior
Connection was properly closed (OK)
GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.5.2-0.5.9 Host: 127.0.0.1:9001 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: 9RiPv08D5FdGMK21opyeQw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Server: AutobahnPython/0.5.9 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: sxiPfchxNu7mEcDUYcjYOYZTXXA=
| Key | Value | Description |
| isServer | False | 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 |
| 159 | 1 | 159 |
| Total | 1 | 159 |
| Chop Size | Count | Octets |
| 4 | 1 | 4 |
| 6 | 1 | 6 |
| 11 | 1 | 11 |
| 239 | 1 | 239 |
| Total | 4 | 260 |
| Opcode | Count |
| Total | 0 |
| Opcode | Count |
| Total | 0 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
322d302e352e390d0a486f73743a203132372e302e302e313a393030310d0a557067726164653a20576562536f636b65740d
0a436f6e6e656374696f6e3a20557067726164650d0a507261676d613a206e6f2d63616368650d0a43616368652d436f6e74
726f6c3a206e6f2d63616368650d0a5365632d576562536f636b65742d4b65793a203952695076303844354664474d4b3231
6f70796551773d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
507974686f6e2f302e352e390d0a557067726164653a20576562536f636b65740d0a436f6e6e656374696f6e3a2055706772
6164650d0a5365632d576562536f636b65742d4163636570743a2073786950666368784e75376d4563445559636a594f595a
545858413d0d0a0d0a
002 TX OCTETS: 01950721746d
003 TX OCTETS: c99b95d0beeef7a3bbefc1
004 DELAY 1.000000 sec for TAG A
005 DELAY TIMEOUT on TAG A
006 TX OCTETS: 9997a1f4
007 DELAY 1.000000 sec for TAG B
008 TCP DROPPED BY PEER