AVR / W5100 / Ethernet - Case 7.9.7 : Pass - 1 ms @ 2025-03-16T00:20:38.622Z

Case Description

Send close with invalid close code 1100

Case Expectation

Clean close with protocol error code 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 / HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: host.docker.internal:9001
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: obGPM3eYXKONQZQ2M4HJQA==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Access-Control-Allow-Origin: *
Connection: Upgrade
Sec-Websocket-Accept: IaT5r6RYYPjzmRZjfOWIvJpYMss=
Upgrade: websocket
Date: Sun, 16 Mar 2025 00:20:38 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	1100	The close code I sent in close frame (if any).
localCloseReason	None	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		The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
37	1	37
198	1	198
Total	2	235

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
251	1	251
Total	2	259

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

               322d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a4163636573732d436f6e74726f6c2d41

               6c6c6f772d4f726967696e3a202a ...

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

003 TX OCTETS: 88820f654cb60b29

004 FAIL CONNECTION AFTER 1.000000 sec

005 RX OCTETS: 882303ea000000000000000000000000000000000000000000000000000000000000000000

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

               0x03ea000000000000000000000000000000000000000000000000000000000000000000

007 TCP DROPPED BY PEER