Autobahn WebSocket Testsuite Report
Autobahn WebSocket

websock-client - Case 12.4.3 : Pass - 451 ms @ 2025-11-26T12:41:08.986Z

Case Description

Send 1000 compressed messages each of payload size 256, auto-fragment to 0 octets. Use default permessage-deflate offer.

Case Expectation

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

Case Outcome

Ok, received all echo'ed messages in time.

Expected:
{}

Observed:
[]

Case Closing Behavior

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



Opening Handshake

GET /runCase?case=358&agent=websock-client HTTP/1.1
Connection: Upgrade
Upgrade: websocket
Host: 127.0.0.1:9001
Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=15
Cache-Control: no-cache
Sec-Websocket-Version: 13
Sec-Websocket-Key: Xon1xKhERz79TwsGtCsZhQ==
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: 09HF40JrPGyxmcpKS6jVpvUofyI=
Sec-WebSocket-Extensions: permessage-deflate


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
264996262944
2701270
2713813
2881288
Total1001264315

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
716112
818144
919
1058580
1136396
1214168
1372936
142082912
15751125
16641024
1758986
1848864
1929551
2040800
2138798
2220440
2318414
2410240
257175
268208
27381
286168
29387
3011330
319279
3210320
33399
347238
355175
366216
373111
385190
393117
403120
41282
42284
435215
443132
465230
48296
49298
502100
512102
523156
533159
54154
55155
56156
59159
603180
61161
62162
63163
65165
694276
71171
72172
73173
742148
79179
80180
81181
82182
83183
872174
88188
892178
92192
932186
97197
99199
1021102
1071107
1081108
1092218
1101110
1121112
1141114
1162232
1211121
1231123
1271127
1331133
1351135
1391139
1471147
1541154
1901190
2541254
Total100222111

Frames Received by Opcode

OpcodeCount
11000
Total1000

Frames Transmitted by Opcode

OpcodeCount
11000
81
Total1001


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d333538266167656e743d776562736f636b2d636c69656e7420485454502f312e
               310d0a436f6e6e656374696f6e3a ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f32352e31 ...
002 WIRELOG DISABLED
003 CLOSE CONNECTION AFTER 120.000000 sec
004 WIRELOG ENABLED
005 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
006 TX OCTETS: 880203e8
007 TCP DROPPED BY PEER