SwiftWebSocket - Case 12.3.2 : Pass - 195 ms @ 2016-04-13T16:12:25.696Z

Case Description

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

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

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: wAcxFeOj1pgg+wZgQT55vs8IKeE=
Sec-WebSocket-Extensions: permessage-deflate; server_max_window_bits=15

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
70	1000	70000
382	1	382
Total	1002	70388

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
14	2	28
15	1	15
16	1	16
17	1	17
18	1	18
19	1	19
20	1	20
21	1	21
22	2	44
24	2	48
25	6	150
26	1	26
27	8	216
28	14	392
29	18	522
30	27	810
31	23	713
32	49	1568
33	69	2277
34	75	2550
35	84	2940
36	90	3240
37	94	3478
38	83	3154
39	79	3081
40	59	2360
41	48	1968
42	42	1764
43	35	1505
44	20	880
45	11	495
46	11	506
47	13	611
48	7	336
49	3	147
50	1	50
51	4	204
52	2	104
53	1	53
54	1	54
55	1	55
57	2	114
58	1	58
59	1	59
60	1	60
62	1	62
64	1	64
67	1	67
279	1	279
Total	1002	37222

Frames Received by Opcode

Opcode	Count
2	1000
8	1
Total	1001

Frames Transmitted by Opcode

Opcode	Count
2	1000
8	1
Total	1001

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d333433266167656e743d5377696674576562536f636b657420485454502f312e

               310d0a5365632d576562536f636b ...

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

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

009 TCP DROPPED BY ME