faye-websocket ruby-3.1 passenger - Case 5.12 : Pass - 1 ms @ 2023-09-07T20:38:48.466Z
Case Description
Send unfragmented Text Message after Continuation Frame with FIN = false, 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.2-0.10.9 Host: 127.0.0.1:7012 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: vlswZ1mUXWUM1lPvXGTjcw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: upgrade Status: 101 Switching Protocols Upgrade: websocket Sec-WebSocket-Accept: 8eIsB5EKO2K6OJNClIMHm+4K79o= Date: Thu, 07 Sep 2023 20:38:48 GMT X-Powered-By: Phusion Passenger(R) 6.0.18 Server: nginx/1.24.0 + Phusion Passenger(R) 6.0.18
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 | Received unexpected continuation frame | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
42 | 1 | 42 |
294 | 1 | 294 |
Total | 2 | 336 |
Chop Size | Count | Octets |
8 | 1 | 8 |
19 | 1 | 19 |
30 | 1 | 30 |
240 | 1 | 240 |
Total | 4 | 297 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
0 | 1 |
1 | 1 |
8 | 1 |
Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
322d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2075706772
6164650d0a5374617475733a2031 ...
002 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=24, MASK=d8a76082, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
non-continuation payload
003 TX OCTETS: 0098d8a76082b6c80eafbbc80ef6b1c915e3acce0fecf8d701fbb4c801e6
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=2549939b, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
005 TX OCTETS: 818d2549939b6d2cfff74a65b3ec4a3bffff04
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 882803ea526563656976656420756e657870656374656420636f6e74696e756174696f6e206672616d65
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=40, MASKED=False, MASK=None
0x03ea526563656976656420756e657870656374656420636f6e74696e756174696f6e206672616d65
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=590bfdf2, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
010 TX OCTETS: 8882590bfdf25ae3
011 TCP DROPPED BY PEER