websock-client - Case 5.9 : Pass - 0 ms @ 2024-11-28T05:32:27.354Z

Case Description

Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in one chop.

Case Expectation

The connection is failed immediately, since there is no message to continue.

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=53&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: pi8CVoq0Cqt3nfYCCkS+GA==

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

Closing Behavior

Key	Value	Description
isServer	True	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	False	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	None	The close code I sent in close frame (if any).
localCloseReason	None	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
287	1	287
Total	1	287

Octets Transmitted by Chop Size

Chop Size	Count	Octets
15	1	15
26	1	26
206	1	206
Total	3	247

Frames Received by Opcode

Opcode	Count
Total	0

Frames Transmitted by Opcode

Opcode	Count
0	1
1	1
Total	2

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3533266167656e743d776562736f636b2d636c69656e7420485454502f312e31

               0d0a436f6e6e656374696f6e3a20 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

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

               non-continuation payload

003 TX OCTETS: 80186e6f6e2d636f6e74696e756174696f6e207061796c6f6164

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

               Hello, world!

005 TX OCTETS: 810d48656c6c6f2c20776f726c6421

006 FAIL CONNECTION AFTER 1.000000 sec

007 TCP DROPPED BY PEER