Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xeda080edb080

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.

Case Outcome

Actual events differ from any expected.

Expected:
{'OK': []}

Observed:
[('message', u'\ufffd\ufffd', False)]

Case Closing Behavior

The connection was failed by the wrong endpoint (FAILED)

Opening Handshake

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

               302d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120576562536f636b65742050726f746f636f6c2048616e647368616b650d0a55706772616465

               3a20576562536f636b65740d0a43 ...

002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=6, MASK=e72f6e80, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               𐀀

003 TX OCTETS: 8186e72f6e800a8fee6d57af

004 FAIL CONNECTION AFTER 0.500000 sec

005 RX OCTETS: 8106efbfbdefbfbd

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

               ��

007 FAILING CONNECTION

008 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=6a389421, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e9476f696e672041776179

009 TX OCTETS: 888c6a38942169d1d34e0356f3012b4ff558

010 RX OCTETS: 810e03efbfbd476f696e672041776179

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

012 TCP DROPPED BY ME

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	True	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 did not respond (in time) in 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	True	When we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode	1001	The close code I sent in close frame (if any).
localCloseReason	Going Away	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
8	1	8
16	1	16
138	1	138
Total	3	162