GoWebSock - Case 7.3.2 : Pass - 1 ms @ 2025-04-20T09:27:40.662Z

Case Description

Send a close frame with payload length 1

Case Expectation

Clean close with protocol error or drop TCP.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET /echo HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: host.docker.internal:8080
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: KfTJScU2vhffMtor0whJPg==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Connection: Upgrade
Sec-WebSocket-Accept: r2J4QXsFACi0waodjR58EqKysMA=
Sec-WebSocket-Version: 13
Server: GoWebSock
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	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	None	The close code I sent in close frame (if any).
localCloseReason	a	The close reason I sent in close frame (if any).
remoteCloseCode	1002	The close code the peer sent me in close frame (if any).
remoteCloseReason	protocol error: close payload length must be 0 or at least 2	The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
64	1	64
175	1	175
Total	2	239

Octets Transmitted by Chop Size

Chop Size	Count	Octets
7	1	7
255	1	255
Total	2	262

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: 474554202f6563686f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f

               302e382e322d302e31302e390d0a ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772

               6164650d0a5365632d576562536f ...

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

003 TX OCTETS: 8881952435c7f4

004 FAIL CONNECTION AFTER 1.000000 sec

005 RX OCTETS: 883e03ea70726f746f636f6c206572726f723a20636c6f7365207061796c6f6164206c656e677468206d7573742062652030

               206f72206174206c656173742032 ...

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

               0x03ea70726f746f636f6c206572726f723a20636c6f7365207061796c6f6164206c656e677468206d757374206265203020

               6f72206174206c656173742032 ...

007 TCP DROPPED BY PEER