libwebsockets - Case 13.2.2 : Pass - 3242 ms @ 2017-10-16T11:00:35.580Z

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=413&agent=libwebsockets HTTP/1.1
Pragma: no-cache
Cache-Control: no-cache
Host: 127.0.0.1:9001
Origin: http://127.0.0.1:9001
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: +n5+FQaL3Ln7HmYUyf2cCA==
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.5-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: u2pBRvumPxqDQBukdErDBVS8L0A=
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 WebSockets 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	3	117
40	9	360
41	18	738
42	49	2058
43	8	344
44	10	440
45	17	765
46	14	644
47	16	752
48	44	2112
49	51	2499
50	32	1600
51	51	2601
52	73	3796
53	84	4452
54	80	4320
55	33	1815
56	55	3080
57	51	2907
58	11	638
59	21	1239
60	13	780
61	29	1769
62	86	5332
63	72	4536
64	34	2176
65	14	910
66	14	924
67	6	402
68	2	136
361	1	361
Total	1002	54611

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

               0d0a507261676d613a206e6f2d63 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e372e ...

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: 88824f2a52f14cc2

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

               0x03e8

009 TCP DROPPED BY ME