ESP8266 / WiFi - Case 6.4.4 : Non-Strict - 2054 ms @ 2020-06-03T17:02:15.479Z
Case Description
Same as Case 6.4.2, but we send message not in 3 frames, but in 3 chops of the same message frame.
MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5f4
PART2 = 90
PART3 =
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 / HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.0-0.10.9 Host: 192.168.46.182:9001 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: gVTbQ+iJ6t92PlS/03hg5Q== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: fXgarZsm2vcBjTc7e75nkiKcYVY=
| 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 WebSocket 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 | None | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 1 | 1 | 1 |
| 3 | 1 | 3 |
| 32 | 1 | 32 |
| 97 | 1 | 97 |
| Total | 4 | 133 |
| Chop Size | Count | Octets |
| 1 | 1 | 1 |
| 6 | 2 | 12 |
| 8 | 2 | 16 |
| 12 | 1 | 12 |
| 245 | 1 | 245 |
| Total | 7 | 286 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 0 | 1 |
| 8 | 1 |
| Total | 2 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c73
002 RX OCTETS: 0d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562
536f636b65742d4163636570743a ...
003 TX OCTETS: 01956f94fd92
004 TX OCTETS: a12e1c2fd65b7e5cd35a4866
005 DELAY 1.000000 sec for TAG A
006 DELAY TIMEOUT on TAG A
007 TX OCTETS: ff
008 DELAY 1.000000 sec for TAG B
009 DELAY TIMEOUT on TAG B
010 TX OCTETS: 147df70bfd89f70b
011 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=3981e7bd, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
012 TX OCTETS: 80803981e7bd
013 FAIL CONNECTION AFTER 1.000000 sec
014 RX OCTETS: 88
015 RX OCTETS: 0203ef
016 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=False, MASK=None
0x03ef
017 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=f99fdb12, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
018 TX OCTETS: 8882f99fdb12fa77
019 TCP DROPPED BY PEER