PocketSocketServer - Case 13.6.2 : Pass - 347 ms @ 2016-03-30T12:12:25.752Z

Case Description

Send 1000 compressed messages each of payload size 64, auto-fragment to 0 octets. Use permessage-deflate client offers (requestNoContextTakeover, requestMaxWindowBits): [(True, 15)]

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 / 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: xrqggE0ABqHwUD/cfR0ANQ==
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits; server_no_context_takeover; server_max_window_bits=15
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Sec-WebSocket-Accept: Mv7TMvoTe7Ib32RzNISqDg9CqT4=
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	488	976
4	1	4
5	216	1080
6	2	12
7	303	2121
8	91	728
9	75	675
10	133	1330
11	58	638
12	41	492
13	50	650
14	18	252
15	7	105
17	1	17
22	1	22
30	1	30
35	1	35
38	1	38
51	1	51
229	1	229
Total	1490	9485

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
11	443	4873
12	10	120
13	137	1781
14	179	2506
15	35	525
16	68	1088
17	78	1326
18	28	504
19	16	304
23	1	23
28	1	28
36	1	36
41	1	41
42	1	42
55	1	55
393	1	393
Total	1002	13653

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

               636570743a204d7637544d766f54 ...

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

               0x03e8

006 TX OCTETS: 888210e4fb7f130c

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