Autobahn WebSocket Testsuite Report
Autobahn WebSocket

websock secure server - Case 2.9 : Pass - 1 ms @ 2026-03-07T18:25:42.707Z

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 /wss HTTP/1.1
User-Agent: AutobahnTestSuite/25.10.1-0.10.9
Host: 127.0.0.1:8889
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: eMits5iIzDP/xuUc/aq7YQ==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Date: Sat, 07 Mar 2026 18:25:42 GMT
Connection: Upgrade
Upgrade: websocket
Sec-Websocket-Accept: itXTqGSf2j/mIkzTBKjhr2gI5ME=


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
2451245
Total4301

Frames Received by Opcode

OpcodeCount
101
Total1

Frames Transmitted by Opcode

OpcodeCount
81
91
101
Total3


Wire Log

000 TX OCTETS: 474554202f77737320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f32
               352e31302e312d302e31302e390d ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205361742c203037204d61
               7220323032362031383a32353a34 ...
002 TX FRAME : OPCODE=10, FIN=True, RSV=0, PAYLOAD-LEN=24, MASK=2dd9d4f4, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               unsolicited pong payload
003 TX OCTETS: 8a982dd9d4f458b7a79b41b0b79d59bcb0d45db6ba930da9b58d41b6b590
004 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=96850c66, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               ping payload
005 TX OCTETS: 898c96850c66e6ec6201b6f56d1ffaea6d02
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=58f00174, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
010 TX OCTETS: 888258f001745b18
011 TCP DROPPED BY PEER