AutobahnPython/0.10.9 - Case 6.4.3 : Pass - 1001 ms @ 2021-07-17T23:53:20.408Z
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:
{'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.8.1-0.10.9 Host: 127.0.0.1:9001 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: HimmHIRhaddpsMtMdEZH4g== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Server: AutobahnPython/0.10.9 X-Powered-By: AutobahnPython/0.10.9 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: Az8sdWh7LxbzTN2kB1irm4fdrvQ=
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 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 |
197 | 1 | 197 |
Total | 1 | 197 |
Chop Size | Count | Octets |
4 | 1 | 4 |
6 | 1 | 6 |
11 | 1 | 11 |
240 | 1 | 240 |
Total | 4 | 261 |
Opcode | Count |
Total | 0 |
Opcode | Count |
Total | 0 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
312d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
507974686f6e2f302e31302e390d ...
002 TX OCTETS: 0195e1999a03
003 TX OCTETS: 2f237bbe585619cd5d572f
004 DELAY 1.000000 sec for TAG A
005 DELAY TIMEOUT on TAG A
006 TX OCTETS: f771191a
007 DELAY 1.000000 sec for TAG B
008 TCP DROPPED BY PEER