Internet Explorer/11.472 - Case 2.9 : Pass - 2 ms @ 2019-01-06T17:12:33.659Z

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=Internet%20Explorer/11.472 HTTP/1.1

Origin: null

Sec-WebSocket-Key: Vs1jH726W3SlPZh49WsL8A==

Connection: Upgrade

Upgrade: websocket

Sec-WebSocket-Version: 13

User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko

Host: 127.0.0.1:9001

Cache-Control: no-cache
HTTP/1.1 101 Switching Protocols

Server: AutobahnTestSuite/0.8.1-0.10.9

X-Powered-By: AutobahnPython/0.10.9

Upgrade: WebSocket

Connection: Upgrade

Sec-WebSocket-Accept: Grm7g/kOBXGZWmOX0L8GGH+DFU8=


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 WebSocket 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).
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
616
18118
3231323
Total3347

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: 474554202f72756e436173653f636173653d3235266167656e743d496e7465726e65742532304578706c6f7265722f31312e
               34373220485454502f312e310d0a ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
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: 8a8c87806220f7e90c47a7f00359ebef0344
008 RX FRAME : OPCODE=10, FIN=True, RSV=0, PAYLOAD-LEN=12, MASKED=True, MASK=3837383036323230
               ping payload
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
010 TX OCTETS: 880203e8
011 RX OCTETS: 888066dafb42
012 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=True, MASK=3636646166623432
013 TCP DROPPED BY ME