faye-websocket ruby-2.5 thin - Case 6.4.2 : Non-Strict - 2038 ms @ 2023-09-07T20:37:35.287Z

Case Description

Same as Case 6.4.1, but in 2nd frame, we send only up to and including the octet making the complete payload invalid.

MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5f4
PART2 = 90
PART3 = 8080656469746564

Case Expectation

The first frame is accepted, we expect to timeout on the first wait. The 2nd frame 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:
{'NON-STRICT': [('timeout', 'A'), ('timeout', 'B')], 'OK': [('timeout', 'A')]}

Observed:
[('timeout', 'A'), ('timeout', 'B')]

Opening Handshake

Closing Behavior

Wire Statistics

Octets Received by Chop Size

Octets Transmitted by Chop Size

Frames Received by Opcode

Frames Transmitted by Opcode

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e

               322d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b

               65740d0a436f6e6e656374696f6e ...

002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=12, MASK=71ee4823, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0xcebae1bdb9cf83cebcceb5f4

003 TX OCTETS: 018c71ee4823bf54a99ec821cbedcd20fdd7

004 DELAY 1.000000 sec for TAG A

005 DELAY TIMEOUT on TAG A

006 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=1, MASK=a76b78b7, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x90

007 TX OCTETS: 0081a76b78b737

008 DELAY 1.000000 sec for TAG B

009 DELAY TIMEOUT on TAG B

010 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=8, MASK=369a8036, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x8080656469746564

011 TX OCTETS: 8088369a8036b61ae5525feee552

012 FAIL CONNECTION AFTER 1.000000 sec

013 RX OCTETS: 882803ef436f756c64206e6f74206465636f646520612074657874206672616d65206173205554462d38

014 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=40, MASKED=False, MASK=None

               0x03ef436f756c64206e6f74206465636f646520612074657874206672616d65206173205554462d38

015 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=50f16c74, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e8

016 TX OCTETS: 888250f16c745319

017 TCP DROPPED BY PEER

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	Could not decode a text frame as UTF-8	The close reason the peer sent me in close frame (if any).

Chop Size	Count	Octets
42	1	42
129	1	129
Total	2	171