WebSocket++ 0.2.0dev - Case 6.4.2 : Pass - 1001 ms @ 2012-10-12T12:13:34Z

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 = ��edited (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

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

               322d302e352e380d0a486f73743a206c6f63616c686f73743a393030320d0a557067726164653a20576562536f636b65740d

               0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a2044636d3132725a6245

               50387147556f6e51544f7046773d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d0a

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772

               6164650d0a5365632d576562536f636b65742d4163636570743a207852565171754b5953584378316d6b6955364638364263

               72342b6b3d0d0a5365727665723a20576562536f636b65742b2b2f302e322e306465760d0a557067726164653a2077656273

               6f636b65740d0a0d0a

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

               κόσμε�

003 TX OCTETS: 018c9dfe839a53446227243100542130366e

004 DELAY 1.000000 sec for TAG A

005 DELAY TIMEOUT on TAG A

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

�

007 TX OCTETS: 00812a63613eba

008 DELAY 1.000000 sec for TAG B

009 RX OCTETS: 881303ef496e76616c696420555446382064617461

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

               �Invalid UTF8 data

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

�

012 TX OCTETS: 88822915ad8b2afd

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	Invalid UTF8 data	The close reason the peer sent me in close frame (if any).

Chop Size	Count	Octets
21	1	21
159	1	159
Total	2	180