Autobahn WebSockets Testsuite Report
Autobahn WebSockets

PocketSocketClient - Case 2.9 : Pass - 2 ms @ 2016-03-30T11:13:41.361Z

Case Description

Send unsolicited pong with payload. Send ping with payload. Verify pong for ping is received.

Case Expectation

Nothing in reply to own Pong, but Pong with payload echo'ed in reply to Ping. Clean close with normal code.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': [('pong', u'ping payload')]}

Observed:
[('pong', u'ping payload')]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET /runCase?case=25&agent=PocketSocketClient HTTP/1.1
Host: localhost:9001
Sec-WebSocket-Key: Ucg5XLDdlkSRDCTmZXAenQ==
Sec-WebSocket-Version: 13
Upgrade: websocket
Origin: http://localhost:9001
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
Connection: upgrade
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.5-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: BpFHKNOX1k6GpRDUaGbTBjPkbiY=


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).
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
616
818
12112
2991299
Total4325

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
14114
26126
2061206
Total4250

Frames Received by Opcode

OpcodeCount
81
101
Total2

Frames Transmitted by Opcode

OpcodeCount
81
91
101
Total3


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3235266167656e743d636f6d2e7a776f70706c652e5053576562536f636b6574
               20485454502f312e310d0a486f73 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e372e ...
002 TX FRAME : OPCODE=10, FIN=True, RSV=0, PAYLOAD-LEN=24, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               unsolicited pong payload
003 TX OCTETS: 8a18756e736f6c69636974656420706f6e67207061796c6f6164
004 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               ping payload
005 TX OCTETS: 890c70696e67207061796c6f6164
006 CLOSE CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 8a8cb3f08aaf
008 RX OCTETS: c399e4c89380ebd6df9febcb
009 RX FRAME : OPCODE=10, FIN=True, RSV=0, PAYLOAD-LEN=12, MASKED=True, MASK=6233663038616166
               ping payload
010 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
011 TX OCTETS: 880203e8
012 RX OCTETS: 88826247658861af
013 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=3632343736353838
               0x03e8
014 TCP DROPPED BY ME