ESP8266 / WiFi - Case 5.9 : Pass - 51 ms @ 2020-06-03T17:02:03.857Z
Case Description
Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in one chop.
Case Expectation
The connection is failed immediately, since there is no message to continue.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
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: o3Y4sKB3kx3VtFXe1AgCUg== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: uovf8uKyYu5FkBcgl2drMGk+XGk=
| 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 | 1002 | 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 |
| 8 | 1 | 8 |
| 19 | 1 | 19 |
| 30 | 1 | 30 |
| 245 | 1 | 245 |
| Total | 4 | 302 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 0 | 1 |
| 1 | 1 |
| 8 | 1 |
| Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c73
002 RX OCTETS: 0d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562
536f636b65742d4163636570743a ...
003 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=24, MASK=f3856a44, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
non-continuation payload
004 TX OCTETS: 8098f3856a449dea046990ea04309aeb1f2587ec052ad3f50b3d9fea0b20
005 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=0e5d9782, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
006 TX OCTETS: 818d0e5d97824638fbee6171b7f5612ffbe62f
007 FAIL CONNECTION AFTER 1.000000 sec
008 RX OCTETS: 88
009 RX OCTETS: 0203ea
010 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=False, MASK=None
0x03ea
011 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=97ae57b2, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
012 TX OCTETS: 888297ae57b29446
013 TCP DROPPED BY PEER