PocketSocketClient - Case 13.2.2 : Pass - 326 ms @ 2016-03-30T11:24:44.525Z

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=PocketSocketClient HTTP/1.1
Host: localhost:9001
Sec-WebSocket-Key: vTkScRxLBjP8PJtltkOQog==
Sec-WebSocket-Version: 13
Upgrade: websocket
Origin: http://localhost:9001
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
Connection: upgrade

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: gIosRyDxpWR5z/pysA3hwClykGY=
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
6	152	912
8	1	8
35	7	245
36	8	288
37	4	148
38	2	76
39	7	273
40	9	360
41	29	1189
42	33	1386
43	18	774
44	14	616
45	21	945
46	30	1380
47	30	1410
48	64	3072
49	51	2499
50	22	1100
51	46	2346
52	67	3484
53	74	3922
54	70	3780
55	57	3135
56	47	2632
57	29	1653
58	13	754
59	13	767
60	15	900
61	27	1647
62	75	4650
63	58	3654
64	32	2048
65	13	845
66	11	726
67	4	268
300	1	300
Total	1154	54192

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
7	443	3101
8	10	80
9	137	1233
10	179	1790
11	35	385
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	9536

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

               7420485454502f312e310d0a486f ...

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: 88822686a360256e

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

               0x03e8

009 TCP DROPPED BY ME