PocketSocketServer - Case 12.1.3 : Pass - 329 ms @ 2016-03-30T11:59:12.786Z

Case Description

Send 1000 compressed messages each of payload size 256, auto-fragment to 0 octets. Use default permessage-deflate offer.

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 / HTTP/1.1
User-Agent: AutobahnTestSuite/0.7.5-0.10.9
Host: 127.0.0.1:9001
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: EtrYXY9Zuc0YNs0geeX5pg==
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Sec-WebSocket-Accept: xEd3Q9flZwpD+8UNV0cOqoezS7g=
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits=15; server_max_window_bits=15
Upgrade: websocket
Connection: Upgrade

Closing Behavior

Key	Value	Description
isServer	False	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	False	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
2	550	1100
4	1	4
11	17	187
12	35	420
13	46	598
14	110	1540
15	75	1125
16	124	1984
17	124	2108
18	87	1566
19	93	1767
20	55	1100
21	63	1323
22	40	880
23	39	897
24	33	792
25	23	575
26	12	312
27	4	108
28	1	28
29	4	116
30	1	30
31	2	62
32	2	64
33	1	33
34	1	34
35	1	35
39	2	78
41	2	82
61	1	61
64	1	64
147	1	147
229	1	229
Total	1552	19449

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
17	43	731
18	71	1278
19	42	798
20	138	2760
21	106	2226
22	98	2156
23	124	2852
24	71	1704
25	74	1850
26	55	1430
27	51	1377
28	38	1064
29	32	928
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
338	1	338
Total	1002	23562

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 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e

               352d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365632d576562536f636b65742d4163

               636570743a20784564335139666c ...

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=b9515788, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e8

006 TX OCTETS: 8882b9515788bab9

007 RX OCTETS: 880203e8

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

               0x03e8

009 TCP DROPPED BY PEER