Autobahn WebSocket Testsuite Report
Autobahn WebSocket

websock-secure-client - Case 5.3 : Pass - 2 ms @ 2025-11-26T12:36:54.101Z

Case Description

Send text Message fragmented into 2 fragments.

Case Expectation

Message is processed and echo'ed back to us.

Case Outcome

Actual events match at least one expected.

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

Observed:
[('message', u'fragment1fragment2', False)]

Case Closing Behavior

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



Opening Handshake

GET /runCase?case=47&agent=websock-secure-client HTTP/1.1
Connection: Upgrade
Upgrade: websocket
Host: 127.0.0.1:9002
Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=15
Cache-Control: no-cache
Sec-Websocket-Version: 13
Sec-Websocket-Key: WQUHByTzl2DmT/8yLF8iXA==
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/25.10.1-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: zDcIqmdnVP95DjRG8DGyB8v609k=


Closing Behavior

KeyValueDescription
isServerTrueTrue, 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
24124
2941294
Total2318

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
11222
2081208
Total4234

Frames Received by Opcode

OpcodeCount
11
Total1

Frames Transmitted by Opcode

OpcodeCount
01
11
81
Total3


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3437266167656e743d776562736f636b2d7365637572652d636c69656e742048
               5454502f312e310d0a436f6e6e65 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f32352e31 ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               fragment1
003 TX OCTETS: 0109667261676d656e7431
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               fragment2
005 TX OCTETS: 8009667261676d656e7432
006 CLOSE CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 819290deadc6f6accca1fdbbc3b2a1b8dfa7f7b3c8a8e4ec
008 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=18, MASKED=True, MASK=3930646561646336
               fragment1fragment2
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
010 TX OCTETS: 880203e8
011 TCP DROPPED BY PEER