Autobahn WebSockets Testsuite Report
Autobahn WebSockets

WebSocketpp/0.5.1-permessagedeflate - Case 12.1.1 : Pass - 192 ms @ 2015-02-27T15:16:47.745Z

Case Description

Send 1000 compressed messages each of payload size 16, 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=306&agent=WebSocketpp/0.5.1-permessagedeflate HTTP/1.1
Connection: Upgrade
Host: localhost:9001
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits
Sec-WebSocket-Key: GJbdUBpqueovCechSNmJSQ==
Sec-WebSocket-Version: 13
Upgrade: websocket
User-Agent: WebSocketpp/0.5.1-permessagedeflate
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.1-0.10.0
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: Gl1MQfFZ69T1OHwXtQV0GchityA=
Sec-WebSocket-Extensions: permessage-deflate


Closing Behavior

KeyValueDescription
isServerTrueTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeTrueTrue, iff I have initiated closing handshake (that is, did send close first).
failedByMeFalseTrue, 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.
droppedByMeTrueTrue, iff I dropped the TCP connection.
wasCleanTrueTrue, iff full WebSockets closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonNoneWhen wasClean == False, the reason what happened.
wasServerConnectionDropTimeoutFalseWhen we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeoutFalseWhen performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeoutFalseWhen we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode1000The close code I sent in close frame (if any).
localCloseReasonNoneThe close reason I sent in close frame (if any).
remoteCloseCode1000The close code the peer sent me in close frame (if any).
remoteCloseReasonNoneThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
818
106146140
112022222
1234408
13961248
1433462
15690
16464
17468
18236
20120
22122
23123
24248
3581358
Total100211217

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
66143684
72021414
834272
996864
1033330
11666
12448
13452
14228
16116
18118
19119
20240
2151215
Total10027070

Frames Received by Opcode

OpcodeCount
11000
81
Total1001

Frames Transmitted by Opcode

OpcodeCount
11000
81
Total1001


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d333036266167656e743d576562536f636b657470702f302e352e312d7065726d
               6573736167656465666c61746520 ...
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: 8882d3618068d089
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=6433363138303638
               0x03e8
009 TCP DROPPED BY ME