faye-websocket ruby-3.1 passenger - Case 6.1.3 : Pass - 2 ms @ 2023-09-07T20:38:50.532Z

Case Description

Send fragmented text message, 3 fragments, first and last of length 0, middle non-empty.

Case Expectation

A message is echo'ed back to us (with payload = payload of middle fragment).

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': [('message', u'middle frame payload', False)]}

Observed:
[('message', u'middle frame payload', False)]

Opening Handshake

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: BUiivFwcvxnbEMOmpPTPKw== Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols Connection: upgrade Status: 101 Switching Protocols Upgrade: websocket Sec-WebSocket-Accept: 4UIMykfXE94sNHOkF+Ja0yke8m0= Date: Thu, 07 Sep 2023 20:38:50 GMT X-Powered-By: Phusion Passenger(R) 6.0.18 Server: nginx/1.24.0 + Phusion Passenger(R) 6.0.18

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: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2075706772

               6164650d0a5374617475733a2031 ...

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

003 TX OCTETS: 0180eb885792

004 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=20, MASK=3ed9f0c5, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               middle frame payload

005 TX OCTETS: 00943ed9f0c553b094a152bcd0a34cb89da01ea991bc52b691a1

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

007 TX OCTETS: 8080b7e5b365

008 CLOSE CONNECTION AFTER 1.000000 sec

009 RX OCTETS: 81146d6964646c65206672616d65207061796c6f6164

010 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=20, MASKED=False, MASK=None

               middle frame payload

011 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=02ad37b4, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e8

012 TX OCTETS: 888202ad37b40145

013 RX OCTETS: 880203e8

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

               0x03e8

015 TCP DROPPED BY PEER

Key	Value	Description
isServer	False	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	True	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	1000	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
4	1	4
22	1	22
294	1	294
Total	3	320