Autobahn WebSocket Testsuite Report
Autobahn WebSocket

websock secure server - Case 1.1.5 : Pass - 1 ms @ 2025-11-26T12:31:52.422Z

Case Description

Send text message message with payload of length 128.

Case Expectation

Receive echo'ed text message (with payload as sent). Clean close with normal code.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': [('message', u'**************************************************************** ...', False)]}

Observed:
[('message', u'**************************************************************** ...', False)]

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: ngNqdVmITq0o06iTC2NyxA==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Date: Wed, 26 Nov 2025 12:31:52 GMT
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Accept: MXMM7J485fAYppfefN75MqoY1e8=


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
1321132
1661166
Total2298

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
1361136
2451245
Total3389

Frames Received by Opcode

OpcodeCount
11
Total1

Frames Transmitted by Opcode

OpcodeCount
11
81
Total2


Wire Log

000 TX OCTETS: 474554202f77737320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f32
               352e31302e312d302e31302e390d ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205765642c203236204e6f
               7620323032352031323a33313a35 ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=128, MASK=963ca44c, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               **************************************************************** ...
003 TX OCTETS: 81fe0080963ca44cbc168e66bc168e66bc168e66bc168e66bc168e66bc168e66bc168e66bc168e66bc168e66bc168e66bc16
               8e66bc168e66bc168e66bc168e66 ...
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 817e00802a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a
               2a2a2a2a2a2a2a2a2a2a2a2a2a2a ...
006 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=128, MASKED=False, MASK=None
               **************************************************************** ...
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=d5565803, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
008 TX OCTETS: 8882d5565803d6be
009 TCP DROPPED BY PEER