Autobahn WebSocket Testsuite Report
Autobahn WebSocket

websock server - Case 2.9 : Pass - 1 ms @ 2025-11-26T12:31:44.768Z

Case Description

Send unsolicited pong with payload. Send ping with payload. Verify pong for ping is received.

Case Expectation

Nothing in reply to own Pong, but Pong with payload echo'ed in reply to Ping. Clean close with normal code.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': [('pong', u'ping payload')]}

Observed:
[('pong', u'ping payload')]

Case Closing Behavior

The spec requires the connection to be failed cleanly here (UNCLEAN)



Opening Handshake

GET /ws HTTP/1.1
User-Agent: AutobahnTestSuite/25.10.1-0.10.9
Host: 127.0.0.1:8888
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: 7fGXAlHvJROfZ68dj/tcdw==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Date: Wed, 26 Nov 2025 12:31:44 GMT
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Accept: DUiBX6pVKKpzQE08vvL/pMgpd9Y=


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).
failedByMeFalseTrue, 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.
droppedByMeFalseTrue, 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).
wasNotCleanReasonpeer dropped the TCP connection without previous WebSocket closing handshakeWhen 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.
localCloseCode1000The close code I sent in close frame (if any).
localCloseReasonNoneThe 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
14114
1661166
Total2180

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
18118
30130
2441244
Total4300

Frames Received by Opcode

OpcodeCount
101
Total1

Frames Transmitted by Opcode

OpcodeCount
81
91
101
Total3


Wire Log

000 TX OCTETS: 474554202f777320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f3235
               2e31302e312d302e31302e390d0a ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205765642c203236204e6f
               7620323032352031323a33313a34 ...
002 TX FRAME : OPCODE=10, FIN=True, RSV=0, PAYLOAD-LEN=24, MASK=d488fdec, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               unsolicited pong payload
003 TX OCTETS: 8a98d488fdeca1e68e83b8e19e85a0ed99cca4e7938bf4f89c95b8e79c88
004 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=a35900c0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               ping payload
005 TX OCTETS: 898ca35900c0d3306ea7832961b9cf3661a4
006 CLOSE CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 8a0c70696e67207061796c6f6164
008 RX FRAME : OPCODE=10, FIN=True, RSV=0, PAYLOAD-LEN=12, MASKED=False, MASK=None
               ping payload
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=8ed7acca, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
010 TX OCTETS: 88828ed7acca8d3f
011 TCP DROPPED BY PEER