WebSockets Protocol Test Report
Autobahn WebSockets

wslay - Case 2.2 : Pass - 0 ms @ 2012-01-09T14:45:54Z

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 / HTTP/1.1
User-Agent: AutobahnWebSocketsTestSuite/0.4.10
Host: localhost:9090
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: 1XblfbzY42LBqvR8wOTYZQ==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: dbuRp1ZBmcZe3CrA2fQjLUyX+1I=


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
15115
1291129
Total3148

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
19119
2011201
Total3228

Frames Received by Opcode

OpcodeCount
81
101
Total2

Frames Transmitted by Opcode

OpcodeCount
81
91
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374
               53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393039300d0a557067726164653a20776562736f
               636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a203158626c
               66627a5934324c4271765238774f54595a513d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d
               0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a20646275
               5270315a426d635a65334372413266516a4c5579582b31493d0d0a0d0a
002 TX FRAME : OPCODE=9, FIN=True, RSV=0, MASK=b1c1a588, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               Hello, world!
003 TX OCTETS: 898db1c1a588f9a4c9e4deed85ffdeb3c9ec90
004 CLOSE CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 8a0d48656c6c6f2c20776f726c6421
006 RX FRAME : OPCODE=10, FIN=True, RSV=0, MASKED=False, MASK=None
               Hello, world!
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=be7b4f75, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
008 TX OCTETS: 8882be7b4f75bd93
009 RX OCTETS: 880203e8
010 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
011 TCP DROPPED BY PEER