Mint - Case 13.4.3 : Pass - 410 ms @ 2024-06-14T19:48:48.904Z

Case Description

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

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

Connection was properly closed (OK)

Opening Handshake

GET /runCase?case=448&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: IGENSae9MwF19cC2k8K1ZQ==
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: 7ctwtT1f6+ucyGTR5St3FTu1b4o=
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits=15

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
17	39	663
18	222	3996
19	81	1539
20	52	1040
21	147	3087
22	102	2244
23	70	1610
24	77	1848
25	67	1675
26	46	1196
27	33	891
28	27	756
29	15	435
30	4	120
31	1	31
32	3	96
34	2	68
35	2	70
37	1	37
39	2	78
41	1	41
42	1	42
43	1	43
46	1	46
65	1	65
70	1	70
151	1	151
302	1	302
Total	1002	22248

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
13	42	546
14	70	980
15	42	630
16	138	2208
17	105	1785
18	99	1782
19	125	2375
20	72	1440
21	76	1596
22	54	1188
23	53	1219
24	38	912
25	29	725
26	22	572
27	10	270
28	4	112
29	5	145
30	1	30
31	2	62
32	1	32
33	2	66
34	1	34
36	1	36
37	1	37
39	1	39
41	2	82
43	1	43
61	1	61
66	1	66
147	1	147
279	1	279
Total	1002	19503

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: 474554202f72756e436173653f636173653d343438266167656e743d4d696e7420485454502f312e310d0a686f73743a206c

               6f63616c686f73743a393030310d ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

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 RX OCTETS: 888284d120898739

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

               0x03e8

009 TCP DROPPED BY ME