Autobahn WebSocket Testsuite Report
Autobahn WebSocket

websock secure server - Case 6.1.3 : Pass - 2 ms @ 2026-01-07T13:35:37.612Z

Case Description

Send fragmented text message, 3 fragments, first and last of length 0, middle non-empty.

Case Expectation

A message is echo'ed back to us (with payload = payload of middle fragment).

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': [('message', u'middle frame payload', False)]}

Observed:
[('message', u'middle frame payload', 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: aXQm96jP1bb96BQxVIeIfg==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Date: Wed, 07 Jan 2026 13:35:37 GMT
Connection: Upgrade
Upgrade: websocket
Sec-Websocket-Accept: 8lhQYrkXz8gVgxS0HxXUtPnbpp8=


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
22122
1661166
Total2188

Octets Transmitted by Chop Size

Chop SizeCountOctets
6212
818
26126
2451245
Total5291

Frames Received by Opcode

OpcodeCount
11
Total1

Frames Transmitted by Opcode

OpcodeCount
02
11
81
Total4


Wire Log

000 TX OCTETS: 474554202f77737320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f32
               352e31302e312d302e31302e390d ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205765642c203037204a61
               6e20323032362031333a33353a33 ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=0, MASK=68da9375, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
003 TX OCTETS: 018068da9375
004 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=20, MASK=50cc2300, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               middle frame payload
005 TX OCTETS: 009450cc23003da547643ca9036622ad4e6570bc42793ca34264
006 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=c34ef61d, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 8080c34ef61d
008 CLOSE CONNECTION AFTER 1.000000 sec
009 RX OCTETS: 81146d6964646c65206672616d65207061796c6f6164
010 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=20, MASKED=False, MASK=None
               middle frame payload
011 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=3078df4d, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
012 TX OCTETS: 88823078df4d3390
013 TCP DROPPED BY PEER