websock-secure-client - Case 5.14 : Pass - 1 ms @ 2024-11-28T05:30:27.767Z
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 /runCase?case=58&agent=websock-secure-client HTTP/1.1 Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=15 Upgrade: websocket Host: 127.0.0.1:9002 Connection: Upgrade Sec-Websocket-Version: 13 Sec-Websocket-Key: s91AZArwckvQ58bNCmcnkA== Cache-Control: no-cache
HTTP/1.1 101 Switching Protocols Server: AutobahnTestSuite/0.8.2-0.10.9 X-Powered-By: AutobahnPython/0.10.9 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: l1pxC6hw80U0vIwFzqAm0OCye9A=
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 |
294 | 1 | 294 |
Total | 1 | 294 |
Chop Size | Count | Octets |
1 | 5 | 5 |
206 | 1 | 206 |
Total | 6 | 211 |
Opcode | Count |
Total | 0 |
Opcode | Count |
0 | 1 |
1 | 1 |
Total | 2 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3538266167656e743d776562736f636b2d7365637572652d636c69656e742048
5454502f312e310d0a5365632d57 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=24, MASK=None, 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=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
Hello, world!
005 FAIL CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 18
007 TX OCTETS: 6e
008 TX OCTETS: 6f
009 TX OCTETS: 6e
010 TCP DROPPED BY PEER