SAMD21 / W5100 / Ethernet - Case 7.3.4 : Pass - 5 ms @ 2020-06-03T17:02:59.209Z

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 / HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.0-0.10.9
Host: 192.168.46.183:9001
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: ewbUh8VLvBddUSIXUy9siA==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: mpouijRfp/fgm/SYLSeAYPe7fH0=

Closing Behavior

Key	Value	Description
isServer	False	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	False	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
16	1	16
21	1	21
22	1	22
32	1	32
54	1	54
Total	5	145

Octets Transmitted by Chop Size

Chop Size	Count	Octets
20	1	20
245	1	245
Total	2	265

Frames Received by Opcode

Opcode	Count
8	1
Total	1

Frames Transmitted by Opcode

Opcode	Count
8	1
Total	1

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e

               302d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c73

002 RX OCTETS: 0d0a557067726164653a20776562736f636b65740d0a

003 RX OCTETS: 436f6e6e656374696f6e3a20557067726164650d0a

004 RX OCTETS: 5365632d576562536f636b65742d4163636570743a206d706f75696a5266702f66676d2f53594c536541595065376648303d

0d0a0d0a

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

               0x03e848656c6c6f20576f726c6421

006 TX OCTETS: 888e3f8d94243c65dc4153e1fb0468e2e6485bac

007 FAIL CONNECTION AFTER 1.000000 sec

008 RX OCTETS: 880e03e848656c6c6f20576f726c6421

009 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=14, MASKED=False, MASK=None

               0x03e848656c6c6f20576f726c6421

010 TCP DROPPED BY PEER