Case Description

Same as Case 6.4.1, but in 2nd frame, we send only up to and including the octet making the complete payload invalid.

MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5f4
PART2 = 90
PART3 = 8080656469746564

Case Expectation

The first frame is accepted, we expect to timeout on the first wait. The 2nd frame should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.

Case Outcome

Actual events match at least one expected.

Expected:
{'NON-STRICT': [('timeout', 'A'), ('timeout', 'B')], 'OK': [('timeout', 'A')]}

Observed:
[('timeout', 'A')]

Opening Handshake

GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.5.5-0.5.14 Host: localhost:9000 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: dvGFI9iIiNOs4woTobMcrA== 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: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e

               352d302e352e31340d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               507974686f6e2f302e352e31340d ...

002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=12, MASK=68ec9a05, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0xcebae1bdb9cf83cebcceb5f4

003 TX OCTETS: 018c68ec9a05a6567bb8d12319cbd4222ff1

004 DELAY 1.000000 sec for TAG A

005 DELAY TIMEOUT on TAG A

006 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=1, MASK=1adc7196, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x90

007 TX OCTETS: 00811adc71968a

008 DELAY 1.000000 sec for TAG B

009 RX OCTETS: 885303ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e6720746578

               74206d6573736167652061742070 ...

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

               0x03ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e672074657874

               206d65737361676520617420706179 ...

011 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=1f6a00f0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e8

012 TX OCTETS: 88821f6a00f01c82

013 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 WebSockets 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	1007	The close code the peer sent me in close frame (if any).
remoteCloseReason	encountered invalid UTF-8 while processing text message at payload octet index 12	The close reason the peer sent me in close frame (if any).

Chop Size	Count	Octets
85	1	85
160	1	160
Total	2	245

Chop Size	Count	Octets
7	1	7
8	1	8
18	1	18
240	1	240
Total	4	273