WebSocketpp/0.5.1-permessagedeflate - Case 12.2.2 : Pass - 162 ms @ 2015-02-27T15:17:20.971Z

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=325&agent=WebSocketpp/0.5.1-permessagedeflate HTTP/1.1
Connection: Upgrade
Host: localhost:9001
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits
Sec-WebSocket-Key: lp4e++J6411nBbZBaApaWw==
Sec-WebSocket-Version: 13
Upgrade: websocket
User-Agent: WebSocketpp/0.5.1-permessagedeflate

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.1-0.10.0
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: SKzGSOUrk3u/CEUlwe7TM0ltTn0=
Sec-WebSocket-Extensions: permessage-deflate

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
11	6	66
13	1	13
20	1	20
40	1	40
56	2	112
58	12	696
59	2	118
60	1	60
62	3	186
63	5	315
64	12	768
65	18	1170
66	30	1980
67	40	2680
68	84	5712
69	123	8487
70	125	8750
71	174	12354
72	196	14112
73	80	5840
74	19	1406
76	65	4940
358	1	358
Total	1002	70191

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
7	6	42
9	1	9
16	1	16
36	1	36
52	2	104
54	12	648
55	2	110
56	1	56
58	3	174
59	5	295
60	12	720
61	18	1098
62	30	1860
63	40	2520
64	84	5376
65	123	7995
66	125	8250
67	174	11658
68	196	13328
69	80	5520
70	19	1330
72	65	4680
215	1	215
Total	1002	66044

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

               6573736167656465666c61746520 ...

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: 88821feaa46b1c02

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

               0x03e8

009 TCP DROPPED BY ME