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

Case Closing Behavior

The connection was failed by the wrong endpoint (FAILED)

Opening Handshake

GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.7.6-0.10.9 Host: 127.0.0.1:9001 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: wIrmihQRHlhW4802Xdsrmg== 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: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e

               362d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e31203130312057656220536f636b65742050726f746f636f6c2048616e647368616b650d0a536572766572

               3a20676f2f6563686f7365727665 ...

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

               fragment1

003 TX OCTETS: 0189937ed077f50cb110fe1bbe03a2

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

               fragment2

005 TX OCTETS: 8189d8489dc3be3afca4b52df3b7ea

006 FAIL CONNECTION AFTER 1.000000 sec

007 RX OCTETS: 0109667261676d656e74318109667261676d656e7432

008 RX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASKED=False, MASK=None

               fragment1

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

               0x03ea7265636569766564206e6f6e2d636f6e74696e756174696f6e2064617461206672616d65207768696c6520696e7369

               646520667261676d656e746564206d ...

010 TX OCTETS: 88c6f39eefcaf0749daf90fb86bc96facfa49cf0c2a99cf09ba39deb8ebe9af181ea97ff9babd3f89dab9efbcfbd9bf783af

               d3f781b99afa8aea95ec8ead9efb ...

011 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None

012 RX OCTETS: 880203e8

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

               0x03e8

014 TCP DROPPED BY PEER

Key	Value	Description
isServer	False	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	True	True, iff I have initiated closing handshake (that is, did send close first).
failedByMe	True	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	1002	The close code I sent in close frame (if any).
localCloseReason	received non-continuation data frame while inside fragmented message	The close reason I sent in close frame (if any).
remoteCloseCode	1000	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
4	1	4
22	1	22
162	1	162
Total	3	188

Chop Size	Count	Octets
15	2	30
76	1	76
240	1	240
Total	4	346