websock-client - Case 7.3.6 : Pass - 0 ms @ 2024-11-28T05:32:38.368Z

Case Description

Send a close frame with close code and close reason which is too long (124) - total frame payload 126 octets

Case Expectation

Clean close with protocol error code or dropped TCP connection.

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=221&agent=websock-client HTTP/1.1
Connection: Upgrade
Upgrade: websocket
Host: 127.0.0.1:9001
Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=15
Cache-Control: no-cache
Sec-Websocket-Version: 13
Sec-Websocket-Key: 80goDAAnORKAVY: no-cache

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: OrXYGgcYuAkLb14JGibdZwblHpw=

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	False	True, iff I dropped the TCP connection.
wasClean	False	True, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReason	peer dropped the TCP connection without previous WebSocket closing handshake	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	****************************************************************************************************************************	The close reason I sent in close frame (if any).
remoteCloseCode	None	The close code the peer sent me in close frame (if any).
remoteCloseReason	None	The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
288	1	288
Total	1	288

Octets Transmitted by Chop Size

Chop Size	Count	Octets
130	1	130
206	1	206
Total	2	336

Frames Received by Opcode

Opcode	Count
Total	0

Frames Transmitted by Opcode

Opcode	Count
8	1
Total	1

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323231266167656e743d776562736f636b2d636c69656e7420485454502f312e

               310d0a5365632d576562736f636b ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

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

               0x03e82a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a

               2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a ...

003 TX OCTETS: 887e007e03e82a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a

               2a2a2a2a2a2a2a2a2a2a2a2a2a2a ...

004 FAIL CONNECTION AFTER 1.000000 sec

005 TCP DROPPED BY PEER