WebSockets Protocol Test Report
Autobahn WebSockets

wslay - Case 9.7.5 : Pass - 870 ms @ 2012-01-09T14:53:10Z

Case Description

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

Case Expectation

Receive echo'ed text 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 /runCase?case=287&agent=wslay HTTP/1.1
Host: localhost:9001
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: VRwS/J14jQ6P8XuzBA6bqw==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Server: AutobahnWebSocketsTestSuite/0.4.10
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: Nl82pBa18Nk4wwXAOuRkxL8HeUk=


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.
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
8216
1811181
102411024
10329991030968
Total10031032189

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
1731173
102810001028000
Total10021028177

Frames Received by Opcode

OpcodeCount
11000
81
Total1001

Frames Transmitted by Opcode

OpcodeCount
11000
81
Total1001


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323837266167656e743d77736c617920485454502f312e310d0a486f73743a20
               6c6f63616c686f73743a393030310d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e3a205570
               67726164650d0a5365632d576562536f636b65742d4b65793a20565277532f4a31346a5136503858757a4241366271773d3d
               0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d0a
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               576562536f636b6574735465737453756974652f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f
               6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a204e6c38327042613138
               4e6b34777758414f75526b784c384865556b3d0d0a0d0a
002 WIRELOG DISABLED
003 CLOSE CONNECTION AFTER 240.000000 sec
004 WIRELOG ENABLED
005 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
006 TX OCTETS: 880203e8
007 RX OCTETS: 888274a8146e7740
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=True, MASK=74a8146e
009 TCP DROPPED BY ME