lluv-websocket - Case 13.1.3 : Pass - 625 ms @ 2016-03-22T17:36:07.437Z

Case Description

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

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 /runCase?case=398&agent=lluv-websocket HTTP/1.1

Host: 127.0.0.1:9001

Upgrade: websocket

Connection: Upgrade

Sec-WebSocket-Key: Cph1MAtDdoYBQ2KGCz52fA==

Sec-WebSocket-Version: 13

Sec-WebSocket-Protocol: echo

Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits

HTTP/1.1 101 Switching Protocols

Server: AutobahnTestSuite/0.7.1-0.10.0

Upgrade: WebSocket

Connection: Upgrade

Sec-WebSocket-Accept: PFdYBx4v+Sy9cJ8zPVAj0o+OiNk=

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
16	1	16
17	60	1020
18	69	1242
19	68	1292
20	163	3260
21	87	1827
22	95	2090
23	113	2599
24	80	1920
25	79	1975
26	57	1482
27	45	1215
28	28	784
29	15	435
30	17	510
31	5	155
32	2	64
33	1	33
34	4	136
35	1	35
37	1	37
39	1	39
40	1	40
43	1	43
44	1	44
47	1	47
52	1	52
54	1	54
70	1	70
149	1	149
290	1	290
Total	1002	22963

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
12	1	12
13	62	806
14	71	994
15	67	1005
16	162	2592
17	87	1479
18	94	1692
19	112	2128
20	81	1620
21	78	1638
22	56	1232
23	45	1035
24	28	672
25	16	400
26	17	442
27	5	135
28	2	56
29	1	29
30	4	120
31	1	31
33	1	33
35	1	35
36	1	36
39	1	39
40	1	40
43	1	43
48	1	48
50	1	50
66	1	66
145	1	145
215	1	215
Total	1002	18872

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

               310d0a486f73743a203132372e30 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e372e ...

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

               0x03e8

006 TX OCTETS: 880203e8

007 RX OCTETS: 8882d2cb7a4cd123

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

               0x03e8

009 TCP DROPPED BY ME