Autobahn WebSockets Testsuite Report
Autobahn WebSockets

Microsoft-HTTPAPI/2.0 - Case 2.9 : Pass - 1010 ms @ 2021-01-02T08:45:24.798Z

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

The spec requires the connection to be failed cleanly here (UNCLEAN)



Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnTestSuite/0.7.5-0.10.9
Host: 127.0.0.1:9001
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: GB4F4lYIj+63iQ1wIuaSzg==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Server: Microsoft-HTTPAPI/2.0
Connection: Upgrade
Sec-WebSocket-Accept: Gl25g/xBYoXcg/KQPeJAaBBOMhw=
Date: Sat, 02 Jan 2021 16:45:24 CST


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.
droppedByMeTrueTrue, iff I dropped the TCP connection.
wasCleanFalseTrue, iff full WebSockets closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonserver did not drop TCP connection (in time)When wasClean == False, the reason what happened.
wasServerConnectionDropTimeoutTrueWhen 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).
remoteCloseCodeNoneThe 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
212
14114
1971197
Total3213

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
18118
30130
2401240
Total4296

Frames Received by Opcode

OpcodeCount
81
101
Total2

Frames Transmitted by Opcode

OpcodeCount
81
91
101
Total3


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e
               352d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a5365727665723a204d69 ...
002 TX FRAME : OPCODE=10, FIN=True, RSV=0, PAYLOAD-LEN=24, MASK=c504b584, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               unsolicited pong payload
003 TX OCTETS: 8a98c504b584b06ac6eba96dd6edb161d1a4b56bdbe3e574d4fda96bd4e0
004 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=25c9e8cd, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               ping payload
005 TX OCTETS: 898c25c9e8cd55a086aa05b989b449a689a9
006 CLOSE CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 8a0c70696e67207061796c6f6164
008 RX FRAME : OPCODE=10, FIN=True, RSV=0, PAYLOAD-LEN=12, MASKED=False, MASK=None
               ping payload
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=831e0488, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
010 TX OCTETS: 8882831e048880f6
011 RX OCTETS: 8800
012 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
013 CLOSING CONNECTION
014 TCP DROPPED BY ME