libwsc - Case 12.3.2 : Pass - 311 ms @ 2025-05-24T04:26:16.024Z

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

Connection was properly closed (OK)

Opening Handshake

GET /runCase?case=338&agent=libwsc HTTP/1.1
Host:192.168.0.26:9001
Upgrade:websocket
Connection:upgrade
Sec-WebSocket-Key:YD1pZW+6SWx71fpJ/OS+oA==
Sec-WebSocket-Version:13
Sec-WebSocket-Extensions:permessage-deflate; client_no_context_takeover; server_no_context_takeover; client_max_window_bits=9
Origin:http://192.168.0.26:9001

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.8.2-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: PvkJDqS6mRJooP0DY6HD+r5uLGA=
Sec-WebSocket-Extensions: permessage-deflate; server_no_context_takeover

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	True	True, iff I dropped the TCP connection.
wasClean	True	True, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReason	None	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	1000	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
8	1	8
47	1	47
52	1	52
54	1	54
55	3	165
57	4	228
58	2	116
59	5	295
60	4	240
61	6	366
62	13	806
63	10	630
64	21	1344
65	42	2730
66	67	4422
67	89	5963
68	135	9180
69	183	12627
70	205	14350
71	151	10721
72	41	2952
73	16	1168
340	1	340
Total	1002	68804

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
43	1	43
48	1	48
50	1	50
51	3	153
53	4	212
54	2	108
55	5	275
56	4	224
57	6	342
58	13	754
59	10	590
60	21	1260
61	42	2562
62	67	4154
63	89	5607
64	135	8640
65	183	11895
66	205	13530
67	151	10117
68	41	2788
69	16	1104
280	1	280
Total	1002	64740

Frames Received by Opcode

Opcode	Count
2	1000
8	1
Total	1001

Frames Transmitted by Opcode

Opcode	Count
2	1000
8	1
Total	1001

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d333338266167656e743d6c696277736320485454502f312e310d0a486f73743a

               3139322e3136382e302e32363a39 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

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 RX OCTETS: 88827d0c5f207ee4

008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=3764306335663230

               0x03e8

009 TCP DROPPED BY ME