websock server - Case 5.12 : Pass - 0 ms @ 2024-11-28T05:30:50.292Z

Case Description

Send unfragmented Text Message after Continuation Frame with FIN = false, 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 /ws HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: 127.0.0.1:8888
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: +xH5HCPH9jkRzVzUdgypMw==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Date: Thu, 28 Nov 2024 05:30:50 GMT
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Accept: uN4F6VJoBGfa89sF8jDpaFlKppg=

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
242	1	242
Total	3	291

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

               382e322d302e31302e390d0a486f ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205468752c203238204e6f

               7620323032342030353a33303a35 ...

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

               non-continuation payload

003 TX OCTETS: 00987168b1d71f07dffa1207dfa31806c4b60501deb95118d0ae1d07d0b3

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

               Hello, world!

005 TX OCTETS: 818d352db7377d48db5b5a0197405a5fdb5314

006 FAIL CONNECTION AFTER 1.000000 sec

007 TCP DROPPED BY PEER