Autobahn WebSocket Testsuite Report
Autobahn WebSocket

UnknownServer - Case 4.1.3 : Pass - 2009 ms @ 2021-02-12T11:14:20.321Z

Case Description

Send small text message, then send frame with reserved non-control Opcode = 5, then send Ping.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': [('message', u'Hello, world!', False)], 'NON-STRICT': []}

Observed:
[('message', u'Hello, world!', False)]

Case Closing Behavior

The connection was failed by the wrong endpoint (FAILED)



Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.0-0.10.9
Host: 127.0.0.1:9001
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: HeXImrRRQTSrsrrRRDX/QQ==
Sec-WebSocket-Version: 13
HTTP/1.1 101 WebSocket Protocol Handshake
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: gGY4tt6SoZm6mjQqPigJF+/I0Nk=


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).
failedByMeTrueTrue, 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 WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonpeer did not respond (in time) in closing handshakeWhen 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.
wasCloseHandshakeTimeoutTrueWhen we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode1001The close code I sent in close frame (if any).
localCloseReasonGoing AwayThe 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
15115
1381138
Total2153

Octets Transmitted by Chop Size

Chop SizeCountOctets
6212
18118
19119
2401240
Total5289

Frames Received by Opcode

OpcodeCount
11
Total1

Frames Transmitted by Opcode

OpcodeCount
11
51
81
91
Total4


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
               302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120576562536f636b65742050726f746f636f6c2048616e647368616b650d0a55706772616465
               3a20576562536f636b65740d0a43 ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=a1ee5643, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               Hello, world!
003 TX OCTETS: 818da1ee5643e98b3a2fcec27634ce9c3a2780
004 TX FRAME : OPCODE=5, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=0a46778b, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
005 TX OCTETS: 85800a46778b
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=1d857159, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 89801d857159
008 FAIL CONNECTION AFTER 1.000000 sec
009 RX OCTETS: 810d48656c6c6f2c20776f726c6421
010 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASKED=False, MASK=None
               Hello, world!
011 FAILING CONNECTION
012 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=2941392c, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e9476f696e672041776179
013 TX OCTETS: 888c2941392c2aa87e43402f5e0c68365855
014 TCP DROPPED BY ME