websock secure server - Case 5.9 : Pass - 0 ms @ 2024-04-24T05:20:12.849Z

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 /wss HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: 127.0.0.1:8889
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: mA3ydYv8yVkuuf8ayhiFNw==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Date: Wed, 24 Apr 2024 05:20:12 GMT
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Accept: Sv+Mft+t0gcbbVWvBhDPCKWDJ4k=

Closing Behavior

Key	Value	Description
isServer	False	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
166	1	166
Total	1	166

Octets Transmitted by Chop Size

Chop Size	Count	Octets
19	1	19
30	1	30
243	1	243
Total	3	292

Frames Received by Opcode

Opcode	Count
Total	0

Frames Transmitted by Opcode

Opcode	Count
0	1
1	1
Total	2

Wire Log

000 TX OCTETS: 474554202f77737320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f30

               2e382e322d302e31302e390d0a48 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205765642c203234204170

               7220323032342030353a32303a31 ...

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

               non-continuation payload

003 TX OCTETS: 80982263cc3f4c0ca212410ca24b4b0db95e560aa3510213ad464e0cad5b

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

               Hello, world!

005 TX OCTETS: 818dd69fe13f9efa8d53b9b3c148b9ed8d5bf7

006 FAIL CONNECTION AFTER 1.000000 sec

007 TCP DROPPED BY PEER