Autobahn WebSockets Testsuite Report
Autobahn WebSockets

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

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).
remoteCloseCodeNoneThe 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
616
70100070000
3821382
Total100270388

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
14228
15115
16116
17117
18118
19119
20120
21121
22244
24248
256150
26126
278216
2814392
2918522
3027810
3123713
32491568
33692277
34752550
35842940
36903240
37943478
38833154
39793081
40592360
41481968
42421764
43351505
4420880
4511495
4611506
4713611
487336
493147
50150
514204
522104
53153
54154
55155
572114
58158
59159
60160
62162
64164
67167
2791279
Total100237222

Frames Received by Opcode

OpcodeCount
21000
81
Total1001

Frames Transmitted by Opcode

OpcodeCount
21000
81
Total1001


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