client - Case 7.3.2 : Pass - 4 ms @ 2023-02-24T01:25:19.021Z

Case Description

Send a close frame with payload length 1

Case Expectation

Clean close with protocol error or drop TCP.

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=217&agent=client HTTP/1.1
Host: localhost:9002
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Key: ZhHsHWTp274fQZby7PytJg==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.8.2-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: Ym2+QHeWqlZ/oAxY9s2wrBev/QU=

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	None	The close code I sent in close frame (if any).
localCloseReason	a	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 close frame payload len, expect 0, >= 2	The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
55	1	55
182	1	182
Total	2	237

Octets Transmitted by Chop Size

Chop Size	Count	Octets
3	1	3
206	1	206
Total	2	209

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: 474554202f72756e436173653f636173653d323137266167656e743d636c69656e7420485454502f312e310d0a486f73743a

               206c6f63616c686f73743a393030 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

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

003 TX OCTETS: 880161

004 FAIL CONNECTION AFTER 1.000000 sec

005 RX OCTETS: 88b13b72a1093898c8674d13cd605f52c2655401c4295d00c0645e52d168421ece685f52cd6c555e816c4302c46a4f529125

1b4c9c2909

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

               0x03ea696e76616c696420636c6f7365206672616d65207061796c6f6164206c656e2c2065787065637420302c203e3d2032

007 TCP DROPPED BY ME