WebSocket++ 0.2.0dev - Case 6.4.3 : Pass - 1001 ms @ 2012-10-12T12:13:35Z
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.8 Host: localhost:9002 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Key: c8NpcAGACi8CQud41MuZAQ== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: Upgrade Sec-WebSocket-Accept: WmT1MHIo2cwRV0lgaywX9HWToaw= 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 | 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 | 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 | 1000 | The close code I sent in close frame (if any). |
localCloseReason | None | The close reason I sent in close frame (if any). |
remoteCloseCode | 1007 | The close code the peer sent me in close frame (if any). |
remoteCloseReason | Invalid UTF8 data | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
21 | 1 | 21 |
159 | 1 | 159 |
Total | 2 | 180 |
Chop Size | Count | Octets |
4 | 1 | 4 |
6 | 1 | 6 |
8 | 1 | 8 |
11 | 1 | 11 |
196 | 1 | 196 |
Total | 5 | 225 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
8 | 1 |
Total | 1 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
322d302e352e380d0a486f73743a206c6f63616c686f73743a393030320d0a557067726164653a20576562536f636b65740d
0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a2063384e706341474143
69384351756434314d755a41513d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772
6164650d0a5365632d576562536f636b65742d4163636570743a20576d54314d48496f3263775256306c6761797758394857
546f61773d0d0a5365727665723a20576562536f636b65742b2b2f302e322e306465760d0a557067726164653a2077656273
6f636b65740d0a0d0a
002 TX OCTETS: 01954d0f9eb3
003 TX OCTETS: 83b57f0ef4c01d7df1c12b
004 DELAY 1.000000 sec for TAG A
005 DELAY TIMEOUT on TAG A
006 TX OCTETS: 47dd8f1e
007 DELAY 1.000000 sec for TAG B
008 RX OCTETS: 881303ef496e76616c696420555446382064617461
009 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
Invalid UTF8 data
010 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=f1438bce, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
011 TX OCTETS: 8882f1438bcef2ab
012 TCP DROPPED BY PEER