WebSockets Protocol Test Report
Autobahn WebSockets

AutobahnClient/0.4.10 - Case 2.2 : Pass - 1 ms @ 2012-01-09T14:53:45Z

Case Description

Send ping with small text payload.

Case Expectation

Pong with payload echo'ed is sent in reply to Ping. Clean close with normal code.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': [('pong', 'Hello, world!')]}

Observed:
[('pong', 'Hello, world!')]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET /runCase?case=18&agent=AutobahnClient/0.4.10 HTTP/1.1
User-Agent: AutobahnWebSockets/0.4.10
Host: localhost:9001
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: gdboqHbWXkuybXIvE0u7WA==
Sec-WebSocket-Version: 8
HTTP/1.1 101 Switching Protocols
Server: AutobahnWebSocketsTestSuite/0.4.10
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: kZvJ8nNItx1GcAx09OlaCDQopPU=


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
818
19119
2341234
Total3261

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
15115
1731173
Total3192

Frames Received by Opcode

OpcodeCount
81
101
Total2

Frames Transmitted by Opcode

OpcodeCount
81
91
Total2


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3138266167656e743d4175746f6261686e436c69656e742f302e342e31302048
               5454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b6574732f302e342e31300d0a486f
               73743a206c6f63616c686f73743a393030310d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e
               3a20557067726164650d0a5365632d576562536f636b65742d4b65793a206764626f71486257586b75796258497645307537
               57413d3d0d0a5365632d576562536f636b65742d56657273696f6e3a20380d0a0d0a
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               576562536f636b6574735465737453756974652f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f
               6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a206b5a764a386e4e4974
               78314763417830394f6c614344516f7050553d0d0a0d0a
002 TX FRAME : OPCODE=9, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               Hello, world!
003 TX OCTETS: 890d48656c6c6f2c20776f726c6421
004 CLOSE CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 8a8d5e05b6c21660daae312996b53177daa67f
006 RX FRAME : OPCODE=10, FIN=True, RSV=0, MASKED=True, MASK=5e05b6c2
               Hello, world!
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
008 TX OCTETS: 880203e8
009 RX OCTETS: 888248f41dbe4b1c
010 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=True, MASK=48f41dbe
011 TCP DROPPED BY ME