wsgo fuzzing client - Case 3.6 : Fail - 2002 ms @ 2025-03-31T15:46:21.613Z

Case Description

Send Ping with RSV = 6.

Case Expectation

The connection is failed immediately, since RSV must be 0.

Case Outcome

Actual events differ from any expected.

Expected:
{'OK': []}

Observed:
[('message', u'Hello, world!', True)]

Case Closing Behavior

The connection was failed by the wrong endpoint (FAILED)

Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: localhost:8080
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: 8M0tlej7nWlxgW1UxQZYoA==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Connection: Upgrade
Sec-Websocket-Accept: aFyUQYVchyjgXvbm4h3LwttvtK4=
Upgrade: websocket

Closing Behavior

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	True	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	True	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 did not respond (in time) in 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	True	When we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode	1001	The close code I sent in close frame (if any).
localCloseReason	Going Away	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).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
15	1	15
129	1	129
Total	2	144

Octets Transmitted by Chop Size

Chop Size	Count	Octets
18	1	18
19	1	19
240	1	240
Total	3	277

Frames Received by Opcode

Opcode	Count
2	1
Total	1

Frames Transmitted by Opcode

Opcode	Count
2	1
8	1
Total	2

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e

               322d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772

               6164650d0a5365632d576562736f ...

002 TX FRAME : OPCODE=2, FIN=True, RSV=6, PAYLOAD-LEN=13, MASK=a93a9ca6, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               Hello, world!

003 TX OCTETS: e28da93a9ca6e15ff0cac616bcd1c648f0c288

004 FAIL CONNECTION AFTER 1.000000 sec

005 RX OCTETS: 820d48656c6c6f2c20776f726c6421

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

               Hello, world!

007 FAILING CONNECTION

008 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=c32d6eff, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e9476f696e672041776179

009 TX OCTETS: 888cc32d6effc0c42990aa4309df825a0f86

010 TCP DROPPED BY ME