non-tls - Case 5.14 : Pass - 6 ms @ 2021-07-05T07:51:27.433Z
Case Description
Send unfragmented Text Message after Continuation Frame with FIN = false, where there is nothing to continue, sent in octet-wise chops.
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 /echo/message HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: localhost:9998 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: aiRTsz3yLOsz3du/iuRLDA== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Content-Length: 0 Date: Mon, 05 Jul 2021 07:51:27 GMT Server: nbio Upgrade: websocket Connection: Upgrade Sec-Websocket-Accept: zgFa1J+UbiYlK/WutV16/D81K/o=
| 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 |
| 199 | 1 | 199 |
| Total | 1 | 199 |
| Chop Size | Count | Octets |
| 1 | 33 | 33 |
| 252 | 1 | 252 |
| Total | 34 | 285 |
| Opcode | Count |
| Total | 0 |
| Opcode | Count |
| 0 | 1 |
| 1 | 1 |
| Total | 2 |
000 TX OCTETS: 474554202f6563686f2f6d65737361676520485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465
737453756974652f302e382e322d ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e74656e742d4c656e6774683a20
300d0a446174653a204d6f6e2c20 ...
002 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=24, MASK=a316ed21, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
non-continuation payload
003 TX OCTETS: 00
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=d48a0d9b, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
Hello, world!
005 FAIL CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 98
007 TX OCTETS: a3
008 TX OCTETS: 16
009 TX OCTETS: ed
010 TX OCTETS: 21
011 TX OCTETS: cd
012 TX OCTETS: 79
013 TX OCTETS: 83
014 TX OCTETS: 0c
015 TX OCTETS: c0
016 TX OCTETS: 79
017 TX OCTETS: 83
018 TX OCTETS: 55
019 TX OCTETS: ca
020 TX OCTETS: 78
021 TX OCTETS: 98
022 TX OCTETS: 40
023 TX OCTETS: d7
024 TX OCTETS: 7f
025 TX OCTETS: 82
026 TX OCTETS: 4f
027 TX OCTETS: 83
028 TX OCTETS: 66
029 TX OCTETS: 8c
030 TX OCTETS: 58
031 TX OCTETS: cf
032 TX OCTETS: 79
033 TX OCTETS: 8c
034 TX OCTETS: 45
035 TX OCTETS: 81
036 TX OCTETS: 8d
037 TX OCTETS: d4
038 TCP DROPPED BY PEER