Autobahn WebSocket Testsuite Report
Autobahn WebSocket

wsgo fuzzing client - Case 6.13.2 : Fail - 1 ms @ 2025-03-31T15:47:24.938Z

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xe020e120e220e320e420e520e620e720e820e920ea20eb20ec20ed20ee20

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

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: etwZooGyOutMBdMTlxtsgw==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Connection: Upgrade
Sec-Websocket-Accept: 7KqbQIqTpziDxF18NgZ1e8Cwv8I=
Upgrade: websocket


Closing Behavior

KeyValueDescription
isServerFalseTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeTrueTrue, iff I have initiated closing handshake (that is, did send close first).
failedByMeTrueTrue, 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.
droppedByMeTrueTrue, iff I dropped the TCP connection.
wasCleanFalseTrue, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonNoneWhen wasClean == False, the reason what happened.
wasServerConnectionDropTimeoutFalseWhen we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeoutFalseWhen performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeoutFalseWhen we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode1007The close code I sent in close frame (if any).
localCloseReasonencountered invalid UTF-8 while processing text message at payload octet index 1The close reason I sent in close frame (if any).
remoteCloseCodeNoneThe close code the peer sent me in close frame (if any).
remoteCloseReasonNoneThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
32132
1291129
Total2161

Octets Transmitted by Chop Size

Chop SizeCountOctets
36136
88188
2401240
Total3364

Frames Received by Opcode

OpcodeCount
11
Total1

Frames Transmitted by Opcode

OpcodeCount
11
81
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
               322d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772
               6164650d0a5365632d576562736f ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=30, MASK=c21cb983, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0xe020e120e220e320e420e520e620e720e820e920ea20eb20ec20ed20ee20
003 TX OCTETS: 819ec21cb983223c58a3203c5aa3263c5ca3243c5ea32a3c50a3283c52a32e3c54a32c3c
004 FAIL CONNECTION AFTER 0.500000 sec
005 RX OCTETS: 811ee020e120e220e320e420e520e620e720e820e920ea20eb20ec20ed20ee20
006 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=82, MASK=a07b09e8, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e672074657874
               206d65737361676520617420706179 ...
007 TX OCTETS: 88d2a07b09e8a3946c86c3147c86d41e7b8dc45b6086d61a6581c45b5cbce65631c8d7136084c55b799acf186c9bd312678f
               800f6c90d45b648dd308688fc55b ...
008 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
009 TCP DROPPED BY ME