ws@8.17.0 - Case 13.4.3 : Pass - 591 ms @ 2024-05-17T17:52:49.214Z

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=ws@8.17.0 HTTP/1.1
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: TheHVP/eN3GJLs2Y5TwzbA==
Connection: Upgrade
Upgrade: websocket
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
Host: localhost: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: hnDmSTDFjcck7bi9qZdymwavIws=
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	42	714
18	70	1260
19	42	798
20	138	2760
21	105	2205
22	99	2178
23	124	2852
24	72	1728
25	76	1900
26	54	1404
27	53	1431
28	39	1092
29	29	841
30	22	660
31	10	310
32	4	128
33	5	165
34	1	34
35	2	70
36	1	36
37	2	74
38	1	38
40	1	40
41	1	41
43	1	43
45	2	90
47	1	47
65	1	65
70	1	70
151	1	151
255	1	255
Total	1002	23488

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

               632d576562536f636b65742d5665 ...

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: 8882525a5c7951b2

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

               0x03e8

009 TCP DROPPED BY ME