WebSocket++/0.5.1-permessagedeflate - Case 6.4.3 : Pass - 1002 ms @ 2015-02-27T15:42:03.408Z

Case Description

Same as Case 6.4.1, but we send message not in 3 frames, but in 3 chops of the same message frame.

MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5
PART2 = f4908080
PART3 = 656469746564

Case Expectation

The first chop is accepted, we expect to timeout on the first wait. The 2nd chop 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')]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnTestSuite/0.7.1-0.10.0
Host: 127.0.0.1:9002
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: haX9M6UpXPxz46Agnwgu2Q==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Connection: upgrade
Sec-WebSocket-Accept: 0HW5Zqg9BJ3s9GzCnXUetxC+VxY=
Server: WebSocketpp/0.5.1-permessagedeflate
Upgrade: websocket

Closing Behavior

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

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
25	1	25
174	1	174
Total	2	199

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
6	1	6
8	1	8
11	1	11
240	1	240
Total	5	269

Frames Received by Opcode

Opcode	Count
8	1
Total	1

Frames Transmitted by Opcode

Opcode	Count
8	1
Total	1

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e

               312d302e31302e300d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2075706772

               6164650d0a5365632d576562536f ...

002 TX OCTETS: 0195725d4d9e

003 TX OCTETS: bce7ac23cb92ce50ce93f8

004 DELAY 1.000000 sec for TAG A

005 DELAY TIMEOUT on TAG A

006 TX OCTETS: 6ae2ddcd

007 DELAY 1.000000 sec for TAG B

008 RX OCTETS: 881703ef496e76616c6964205554463820656e636f64696e67

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

               0x03ef496e76616c6964205554463820656e636f64696e67

010 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=3619f81c, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e8

011 TX OCTETS: 88823619f81c35f1

012 TCP DROPPED BY PEER