Chrome/71.0.3578.98 - Case 4.1.1 : Pass - 1 ms @ 2019-01-06T16:44:15.808Z

Case Description

Send frame with reserved non-control Opcode = 3.

Case Expectation

The connection is failed immediately.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET /runCase?case=35&agent=Chrome/71.0.3578.98 HTTP/1.1

Host: 127.0.0.1:9001

Connection: Upgrade

Pragma: no-cache

Cache-Control: no-cache

User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Upgrade: websocket

Origin: file://

Sec-WebSocket-Version: 13

Accept-Encoding: gzip, deflate, br

Accept-Language: en-US,en;q=0.9,ca;q=0.8,es;q=0.7

Sec-WebSocket-Key: x8rarPYk9CTIteRxv6EptA==

Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
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: BZvusX5D5UBMcdK6Hk23GNtRF+M=


Closing Behavior

KeyValueDescription
isServerTrueTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeFalseTrue, 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).
remoteCloseCode1002The close code the peer sent me in close frame (if any).
remoteCloseReasonUnknown opcodeThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
22122
5391539
Total2561

Octets Transmitted by Chop Size

Chop SizeCountOctets
212
414
2061206
Total3212

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
31
81
Total2


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3335266167656e743d4368726f6d652f37312e302e333537382e393820485454
               502f312e310d0a486f73743a2031 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=3, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
003 TX OCTETS: 8300
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 8890a9588d7caab2d812c236e20bc778e20cca37e919
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=16, MASKED=True, MASK=6139353838643763
               0x03ea556e6b6e6f776e206f70636f6465
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
008 TX OCTETS: 880203e8
009 TCP DROPPED BY ME