Case Description

Send text Message fragmented into 2 fragments, with both frame opcodes set to text, sent in one chop.

Case Expectation

The connection is failed immediately, since all data frames after the initial data frame must have opcode 0.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

Opening Handshake

GET /echo 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: 5Rw/AGgdLaWSHooVWM3q2Q== 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: 474554202f6563686f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f

               302e382e322d302e31302e390d0a ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772

               6164650d0a5365632d576562536f ...

002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=801354ea, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               fragment1

003 TX OCTETS: 0189801354eae661358ded763a9eb1

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

               fragment2

005 TX OCTETS: 81890c7f773e6a0d1659611a194a3e

006 FAIL CONNECTION AFTER 1.000000 sec

007 RX OCTETS: 883503ea6e65772064617461206672616d65207265636569766564207768696c6520696e20667261676d656e746564206d65

7373616765

008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=53, MASKED=False, MASK=None

               0x03ea6e65772064617461206672616d65207265636569766564207768696c6520696e20667261676d656e746564206d6573

73616765

009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=019bef33, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e8

010 TX OCTETS: 8882019bef330273

011 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	True	True, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReason	None	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	None	The close reason I sent in close frame (if any).
remoteCloseCode	1002	The close code the peer sent me in close frame (if any).
remoteCloseReason	new data frame received while in fragmented message	The close reason the peer sent me in close frame (if any).

Chop Size	Count	Octets
8	1	8
15	2	30
255	1	255
Total	4	293