websock-client - Case 12.4.2 : Pass - 445 ms @ 2025-11-26T12:41:08.540Z

Case Description

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

Case Expectation

Receive echo'ed messages (with payload as sent). Timeout case after 60 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=357&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: N6x9Rvq8UsQTGuD+x/u/+A==

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: pVeOX5r40vIUJPOLu8b64zCzkVg=
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	True	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	1000	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
70	1000	70000
288	1	288
Total	1001	70288

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
7	564	3948
8	5	40
9	56	504
10	32	320
11	9	99
12	21	252
13	127	1651
14	33	462
15	14	210
16	5	80
17	6	102
18	10	180
19	10	190
20	9	180
21	4	84
22	6	132
23	5	115
24	8	192
25	5	125
26	10	260
27	7	189
28	3	84
29	3	87
30	4	120
31	2	62
32	2	64
33	4	132
34	2	68
35	4	140
36	1	36
37	1	37
38	3	114
39	1	39
40	3	120
41	2	82
42	1	42
43	1	43
46	2	92
47	2	94
48	2	96
49	1	49
50	2	100
51	1	51
52	1	52
53	2	106
55	1	55
57	1	57
58	1	58
59	1	59
254	1	254
Total	1002	11712

Frames Received by Opcode

Opcode	Count
1	1000
Total	1000

Frames Transmitted by Opcode

Opcode	Count
1	1000
8	1
Total	1001

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d333537266167656e743d776562736f636b2d636c69656e7420485454502f312e

               310d0a436f6e6e656374696f6e3a ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f32352e31 ...

002 WIRELOG DISABLED

003 CLOSE CONNECTION AFTER 60.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