wslay - Case 6.4.3 : Pass - 1002 ms @ 2012-01-09T14:51:48Z
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 /runCase?case=76&agent=wslay HTTP/1.1 Host: localhost:9001 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: mYp0bter0LTW+aRzr11HRA== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Server: AutobahnWebSocketsTestSuite/0.4.10 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: +GxvNiyyKsm1kM2n5wQXuGWF6zE=
| 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 | 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. |
| 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 | None | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 180 | 1 | 180 |
| Total | 2 | 188 |
| Chop Size | Count | Octets |
| 2 | 1 | 2 |
| 4 | 2 | 8 |
| 11 | 1 | 11 |
| 173 | 1 | 173 |
| Total | 5 | 194 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3736266167656e743d77736c617920485454502f312e310d0a486f73743a206c
6f63616c686f73743a393030310d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e3a20557067
726164650d0a5365632d576562536f636b65742d4b65793a206d59703062746572304c54572b61527a7231314852413d3d0d
0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d0a
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
576562536f636b6574735465737453756974652f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f
6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a202b4778764e6979794b
736d316b4d326e3577515875475746367a453d0d0a0d0a
002 TX OCTETS: 0115
003 TX OCTETS: cebae1bdb9cf83cebcceb5
004 DELAY 1.000000 sec for TAG A
005 DELAY TIMEOUT on TAG A
006 TX OCTETS: f4908080
007 DELAY 1.000000 sec for TAG B
008 RX OCTETS: 8882a8aea7fbab41
009 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=True, MASK=a8aea7fb
010 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
011 TX OCTETS: 880203e8
012 TCP DROPPED BY ME