yawc - Case 7.3.4 : Pass - 2 ms @ 2018-04-16T14:00:56.413Z

Case Description

Send a close frame with close code and close reason

Case Expectation

Clean close with normal code.

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=219&agent=yawc HTTP/1.1
Sec-WebSocket-Key: sawY3QQO2BW5alUt9GJ3qg==
Host: autobahn-server:9001
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.6-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: KLQHxVNLQyavWunIPNFEaA6/lpM=

Closing Behavior

Key	Value	Description
isServer	True	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	True	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 WebSocket 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	Hello World!	The close reason I sent in close frame (if any).
remoteCloseCode	1000	The close code the peer sent me in close frame (if any).
remoteCloseReason	Hello World!	The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
20	1	20
186	1	186
Total	2	206

Octets Transmitted by Chop Size

Chop Size	Count	Octets
16	1	16
206	1	206
Total	2	222

Frames Received by Opcode

Opcode	Count
8	1
Total	1

Frames Transmitted by Opcode

Opcode	Count
8	1
Total	1

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323139266167656e743d7961776320485454502f312e310d0a5365632d576562

               536f636b65742d4b65793a207361 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e372e ...

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

               0x03e848656c6c6f20576f726c6421

003 TX OCTETS: 880e03e848656c6c6f20576f726c6421

004 FAIL CONNECTION AFTER 1.000000 sec

005 RX OCTETS: 888e95b887af9650cfcaf9d4e88fc2d7f5c3f199

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

               0x03e848656c6c6f20576f726c6421

007 TCP DROPPED BY ME