Autobahn WebSockets Testsuite Report
Autobahn WebSockets

Microsoft-HTTPAPI/2.0 - Case 3.1 : Fail - 2010 ms @ 2021-01-02T08:45:28.029Z

Case Description

Send small text message with RSV = 1.

Case Expectation

The connection is failed immediately (1002/protocol error), since RSV must be 0, when no extension defining RSV meaning has been negotiated.

Case Outcome

Actual events differ from any expected.

Expected:
{'OK': []}

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.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: OohBDF1eUGRj0nxTNJ0NJw==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Server: Microsoft-HTTPAPI/2.0
Connection: Upgrade
Sec-WebSocket-Accept: qT/KazI0/n0WYiuLfyKj0Z4YSQI=
Date: Sat, 02 Jan 2021 16:45:28 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).
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 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.
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
212
15115
1971197
Total3214

Octets Transmitted by Chop Size

Chop SizeCountOctets
18118
19119
2401240
Total3277

Frames Received by Opcode

OpcodeCount
11
81
Total2

Frames Transmitted by Opcode

OpcodeCount
11
81
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e
               352d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a5365727665723a204d69 ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=1, PAYLOAD-LEN=13, MASK=e97c9010, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               Hello, world!
003 TX OCTETS: 918de97c9010a119fc7c8650b067860efc74c8
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 810d48656c6c6f2c20776f726c6421
006 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASKED=False, MASK=None
               Hello, world!
007 FAILING CONNECTION
008 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=d51f4cc4, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e9476f696e672041776179
009 TX OCTETS: 888cd51f4cc4d6f60babbc712be494682dbd
010 RX OCTETS: 8800
011 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
012 TCP DROPPED BY ME