ws://localhost:8080/websocket-endpoints/echoBasicEndpoint - Case 7.9.1 : Fail - 1 ms @ 2025-12-05T17:53:44.032Z

Case Description

Send close with invalid close code 0

Case Expectation

Clean close with protocol error code or drop TCP

Case Outcome

The close code should have been 1002 or empty

Expected:
{'OK': []}

Observed:
[]

Case Closing Behavior

The close code should have been 1002 or empty (WRONG CODE)

Opening Handshake

GET /websocket-endpoints/echoBasicEndpoint HTTP/1.1
User-Agent: AutobahnTestSuite/25.10.1-0.10.9
Host: localhost:8080
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: 0eWbAX1pkJ+v4lOSW/3nLA==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Connection: Upgrade
Sec-WebSocket-Location: ws://localhost:8080/websocket-endpoints/echoBasicEndpoint
Upgrade: WebSocket
Sec-WebSocket-Accept: jnTfc1QrbXnYs8ocsXAD10RmKl4=
Date: Fri, 05 Dec 2025 17:53:44 GMT

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	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	0	The close code I sent in close frame (if any).
localCloseReason	None	The close reason I sent in close frame (if any).
remoteCloseCode	1003	The close code the peer sent me in close frame (if any).
remoteCloseReason	UT002026: Invalid close frame status code: 0	The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
48	1	48
249	1	249
Total	2	297

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
279	1	279
Total	2	287

Frames Received by Opcode

Opcode	Count
8	1
Total	1

Frames Transmitted by Opcode

Opcode	Count
8	1
Total	1

Wire Log

000 TX OCTETS: 474554202f776562736f636b65742d656e64706f696e74732f6563686f4261736963456e64706f696e7420485454502f312e

               310d0a557365722d4167656e743a ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772

               6164650d0a5365632d576562536f ...

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

003 TX OCTETS: 8882f8563df1f856

004 FAIL CONNECTION AFTER 1.000000 sec

005 RX OCTETS: 882e03eb55543030323032363a20496e76616c696420636c6f7365206672616d652073746174757320636f64653a2030

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

               0x03eb55543030323032363a20496e76616c696420636c6f7365206672616d652073746174757320636f64653a2030

007 TCP DROPPED BY PEER