SwiftWebSocket - Case 13.3.3 : Pass - 200 ms @ 2016-04-13T16:16:28.671Z

Case Description

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

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=434&agent=SwiftWebSocket HTTP/1.1
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits; server_max_window_bits=8
Upgrade: websocket
User-Agent: SwiftWebSocket
Origin: ws://localhost:9001/runCase?case=434&agent=SwiftWebSocket
Sec-WebSocket-Version: 13
Connection: Upgrade
Host: localhost:9001
Sec-WebSocket-Key: 2O3sp2WFg1AZ+OZ5O5042A==

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.2-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: 3ey9WzVhEOmFQoMK47Vx2YDnlmM=
Sec-WebSocket-Extensions: permessage-deflate; server_max_window_bits=8; client_max_window_bits=8

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	None	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	1	6
264	1000	264000
381	1	381
Total	1002	264387

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
13	1	13
14	97	1358
15	2	30
16	23	368
17	33	561
18	173	3114
19	42	798
20	78	1560
21	160	3360
22	59	1298
23	72	1656
24	76	1824
25	44	1100
26	35	910
27	25	675
28	30	840
29	12	348
30	9	270
31	6	186
32	5	160
33	2	66
34	1	34
35	3	105
36	2	72
38	2	76
40	1	40
41	2	82
44	1	44
49	1	49
67	1	67
72	1	72
147	1	147
304	1	304
Total	1002	21591

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

               310d0a5365632d576562536f636b ...

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: 8880e0537aa3

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

009 TCP DROPPED BY ME