PocketSocketClient - Case 4.2.2 : Pass - 1 ms @ 2016-03-30T11:13:41.574Z

Case Description

Send frame with reserved control Opcode = 12 and non-empty payload.

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=41&agent=PocketSocketClient HTTP/1.1
Host: localhost:9001
Sec-WebSocket-Key: kYlTbtxKMCE09JR2dIJ4Yg==
Sec-WebSocket-Version: 13
Upgrade: websocket
Origin: http://localhost:9001
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
Connection: upgrade

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.5-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: PWzMqx+B0ptArkYXXjU5bq7wgoI=

Closing Behavior

Key	Value	Description
isServer	True	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	False	True, iff I have initiated closing handshake (that is, did send close first).
failedByMe	False	True, 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.
droppedByMe	True	True, iff I dropped the TCP connection.
wasClean	True	True, iff full WebSockets closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReason	None	When wasClean == False, the reason what happened.
wasServerConnectionDropTimeout	False	When we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeout	False	When performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeout	False	When we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode	1000	The close code I sent in close frame (if any).
localCloseReason	None	The close reason I sent in close frame (if any).
remoteCloseCode	1002	The close code the peer sent me in close frame (if any).
remoteCloseReason	Invalid opcode	The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
22	1	22
299	1	299
Total	2	321

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
25	1	25
206	1	206
Total	3	235

Frames Received by Opcode

Opcode	Count
8	1
Total	1

Frames Transmitted by Opcode

Opcode	Count
8	1
12	1
Total	2

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3431266167656e743d636f6d2e7a776f70706c652e5053576562536f636b6574

               20485454502f312e310d0a486f73 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e372e ...

002 TX FRAME : OPCODE=12, FIN=True, RSV=0, PAYLOAD-LEN=23, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               reserved opcode payload

003 TX OCTETS: 8c177265736572766564206f70636f6465207061796c6f6164

004 FAIL CONNECTION AFTER 1.000000 sec

005 RX OCTETS: 88900486f07e076cb91072e79c1760a69f0e67e9941b

006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=16, MASKED=True, MASK=3034383666303765

               0x03ea496e76616c6964206f70636f6465

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