async-client - Case 7.13.1 : Informational - 4 ms @ 2023-02-24T01:34:16.143Z

Case Description

Send close with close code 5000

Case Expectation

Actual events are undefined by the spec.

Case Outcome

Actual events are undefined by the spec.

Expected:
{'OK': []}

Observed:
[]

Case Closing Behavior

Connection was properly closed (INFORMATIONAL)

Opening Handshake

GET /runCase?case=245&agent=async-client HTTP/1.1
Host: localhost:9002
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Key: hVXFNlM/nNlnNeKy7zAefA==
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: LufAjhSMZQlaSr/tec/v4vsxtxk=

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	5000	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 close code 5000	The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
31	1	31
188	1	188
Total	2	219

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
206	1	206
Total	2	210

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

               0a486f73743a206c6f63616c686f ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

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

               0x1388

003 TX OCTETS: 88021388

004 FAIL CONNECTION AFTER 1.000000 sec

005 RX OCTETS: 8899bbb4fe51b85e973fcdd59238df949d3dd4c79b71d8db9a349b81ce618b

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

               0x03ea696e76616c696420636c6f736520636f64652035303030

007 TCP DROPPED BY ME