stratus@2 - Case 13.1.14 : Fail - 2 ms @ 2026-04-02T17:22:54.219Z

Case Description

Send 1000 compressed messages each of payload size 65536, auto-fragment to 256 octets. Use permessage-deflate client offers (requestNoContextTakeover, requestMaxWindowBits): [(False, 0)]

Case Expectation

Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

Case Outcome

Case did not finish within 480 seconds.

Expected:
{}

Observed:
[]

Case Closing Behavior

The connection was failed by the wrong endpoint (FAILED)

Opening Handshake

GET /runCase?case=405&agent=stratus%402 HTTP/1.1
host: 127.0.0.1:9001
upgrade: websocket
connection: upgrade
sec-websocket-key: 1vCU99vWIE0sJ9cJVoUqGA==
sec-websocket-version: 13
sec-websocket-extensions: permessage-deflate

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: dXaEb/m4YzjtLqLpDEq003z0WYs=
Sec-WebSocket-Extensions: permessage-deflate

Closing Behavior

Key	Value	Description
isServer	True	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	False	True, iff I have initiated closing handshake (that is, did send close first).
failedByMe	False	True, 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.
droppedByMe	False	True, iff I dropped the TCP connection.
wasClean	False	True, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReason	peer dropped the TCP connection without previous WebSocket closing handshake	When wasClean == False, the reason what happened.
wasServerConnectionDropTimeout	False	When we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeout	False	When performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeout	False	When we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode	None	The close code I sent in close frame (if any).
localCloseReason	None	The close reason I sent in close frame (if any).
remoteCloseCode	None	The close code the peer sent me in close frame (if any).
remoteCloseReason	None	The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
233	1	233
Total	1	233

Octets Transmitted by Chop Size

Chop Size	Count	Octets
106	1	106
254	1	254
260	11	2860
Total	13	3220

Frames Received by Opcode

Opcode	Count
Total	0

Frames Transmitted by Opcode

Opcode	Count
0	11
1	1
Total	12

Wire Log

Wire log after handshake disabled!

000 RX OCTETS: 474554202f72756e436173653f636173653d343035266167656e743d737472617475732534303220485454502f312e310d0a

               686f73743a203132372e302e302e ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f32352e31 ...

002 WIRELOG DISABLED

003 CLOSE CONNECTION AFTER 480.000000 sec

004 TCP DROPPED BY PEER