Case Description

Send unfragmented Text Message after Continuation Frame with FIN = false, where there is nothing to continue, sent in octet-wise chops.

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:
[]

Opening Handshake

GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: host.docker.internal:8080 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: qaELMGsBpEbrXm9F+0x9Xg== Sec-WebSocket-Version: 13

Closing Behavior

Wire Statistics

Octets Received by Chop Size

Octets Transmitted by Chop Size

Frames Received by Opcode

Frames Transmitted by Opcode

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e

               322d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b

               65740d0a436f6e6e656374696f6e ...

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

               non-continuation payload

003 TX OCTETS: 00

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

               Hello, world!

005 FAIL CONNECTION AFTER 1.000000 sec

006 TX OCTETS: 98

007 TX OCTETS: 72

008 TX OCTETS: 21

009 TX OCTETS: 3d

010 TX OCTETS: 07

011 TX OCTETS: 1c

012 TX OCTETS: 4e

013 TX OCTETS: 53

014 TX OCTETS: 2a

015 TX OCTETS: 11

016 TX OCTETS: 4e

017 TX OCTETS: 53

018 TX OCTETS: 73

019 TX OCTETS: 1b

020 TX OCTETS: 4f

021 TX OCTETS: 48

022 TX OCTETS: 66

023 TX OCTETS: 06

024 TX OCTETS: 48

025 TX OCTETS: 52

026 TX OCTETS: 69

027 TX OCTETS: 52

028 TX OCTETS: 51

029 TX OCTETS: 5c

030 TX OCTETS: 7e

031 TX OCTETS: 1e

032 TX OCTETS: 4e

033 TX OCTETS: 5c

034 TX OCTETS: 63

035 TX OCTETS: 81

036 TX OCTETS: 8d

037 TCP DROPPED BY PEER

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).

Chop Size	Count	Octets
129	1	129
Total	1	129