web-sct 0.2.0 - Case 6.4.3 : Non-Strict - 2007 ms @ 2021-01-18T16:52:49.015Z
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 = 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:
{'OK': [('timeout', 'A')], 'NON-STRICT': [('timeout', 'A'), ('timeout', 'B')]}
Observed:
[('timeout', 'A'), ('timeout', 'B')]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=76&agent=web-sct%200.2.0 HTTP/1.1 Host: localhost:5555 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: 4bgf/kn6u64S8yIOycdGNQ== Sec-WebSocket-Version: 13 Content-Length: 0
HTTP/1.1 101 Switching Protocols Server: AutobahnTestSuite/0.8.0-0.10.9 X-Powered-By: AutobahnPython/0.10.9 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: MlJIyy/r2jXf71PQFdUtlZpMZXM=
| 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 WebSocket 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 |
| 209 | 1 | 209 |
| Total | 1 | 209 |
| Chop Size | Count | Octets |
| 2 | 2 | 4 |
| 4 | 1 | 4 |
| 6 | 1 | 6 |
| 11 | 1 | 11 |
| 206 | 1 | 206 |
| Total | 6 | 231 |
| Opcode | Count |
| Total | 0 |
| Opcode | Count |
| 0 | 1 |
| Total | 1 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3736266167656e743d7765622d736374253230302e322e3020485454502f312e
310d0a486f73743a206c6f63616c ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
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 DELAY TIMEOUT on TAG B
009 TX OCTETS: 656469746564
010 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
011 TX OCTETS: 8000
012 FAIL CONNECTION AFTER 1.000000 sec
013 TCP DROPPED BY PEER