Mint - Case 13.2.2 : Pass - 393 ms @ 2024-06-14T19:48:35.085Z

Case Description

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

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=411&agent=Mint HTTP/1.1
host: localhost:9001
user-agent: mint/1.6.1
upgrade: websocket
connection: upgrade
sec-websocket-version: 13
sec-websocket-key: Fy/v2bBmv6gh7oFgz6897A==
sec-websocket-extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits

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: +/PlMvBWPyEZn4F9VLH+eoYM/Mc=
Sec-WebSocket-Extensions: permessage-deflate; client_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
39	5	195
40	8	320
41	31	1271
42	35	1470
43	11	473
44	15	660
45	17	765
46	20	920
47	22	1034
48	56	2688
49	54	2646
50	16	800
51	50	2550
52	76	3952
53	83	4399
54	84	4536
55	61	3355
56	40	2240
57	21	1197
58	11	638
59	16	944
60	11	660
61	30	1830
62	89	5518
63	68	4284
64	36	2304
65	14	910
66	15	990
67	5	335
302	1	302
Total	1002	54194

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
7	441	3087
8	10	80
9	143	1287
10	174	1740
11	36	396
12	68	816
13	78	1014
14	28	392
15	16	240
19	1	19
24	1	24
32	1	32
37	1	37
38	1	38
51	1	51
280	1	280
Total	1002	9537

Frames Received by Opcode

Opcode	Count
1	1000
8	1
Total	1001

Frames Transmitted by Opcode

Opcode	Count
1	1000
8	1
Total	1001

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d343131266167656e743d4d696e7420485454502f312e310d0a686f73743a206c

               6f63616c686f73743a393030310d ...

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: 8882d967300dda8f

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

               0x03e8

009 TCP DROPPED BY ME