WebSockets Protocol Test Report
Autobahn WebSockets

AutobahnServer/0.4.10 - Case 9.8.5 : Pass - 1025 ms @ 2012-01-09T14:45:49Z

Case Description

Send 1000 binary messages of payload size 1024 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed binary messages (with payload as sent). Timeout case after 240 secs.

Case Outcome

Ok, received all echo'ed messages in time.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnWebSocketsTestSuite/0.4.10
Host: localhost:9000
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: 0Vy8qg2JlQRVpUqcEQu5Pg==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Server: AutobahnWebSockets/0.4.10
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: T22n7fQCwEQoJ7i6+AihiQQqz2M=


Closing Behavior

KeyValueDescription
isServerFalseTrue, 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.
droppedByMeFalseTrue, 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.
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
414
1641164
102810001028000
Total10021028168

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
2011201
103210001032000
Total10021032209

Frames Received by Opcode

OpcodeCount
21000
81
Total1001

Frames Transmitted by Opcode

OpcodeCount
21000
81
Total1001


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374
               53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393030300d0a557067726164653a20776562736f
               636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a2030567938
               7167324a6c515256705571634551753550673d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d
               0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               576562536f636b6574732f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e3a
               20557067726164650d0a5365632d576562536f636b65742d4163636570743a205432326e376651437745516f4a3769362b41
               6968695151717a324d3d0d0a0d0a
002 WIRELOG DISABLED
003 CLOSE CONNECTION AFTER 240.000000 sec
004 WIRELOG ENABLED
005 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=4fc6caf9, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
006 TX OCTETS: 88824fc6caf94c2e
007 RX OCTETS: 880203e8
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
009 TCP DROPPED BY PEER