WebSocketpp/0.5.1-permessagedeflate - Case 6.4.4 : Pass - 1002 ms @ 2015-02-27T15:15:49.416Z

Case Description

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

MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5f4
PART2 = 90
PART3 =

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 /runCase?case=77&agent=WebSocketpp/0.5.1-permessagedeflate HTTP/1.1
Connection: Upgrade
Host: localhost:9001
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits
Sec-WebSocket-Key: 8uxlLCKPnCf97L4aVvlSVA==
Sec-WebSocket-Version: 13
Upgrade: websocket
User-Agent: WebSocketpp/0.5.1-permessagedeflate

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.1-0.10.0
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: +Z4GjDSthsmO+YOQwQ6I7yWycAg=

Closing Behavior

Key	Value	Description
isServer	True	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	True	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
29	1	29
357	1	357
Total	2	386

Octets Transmitted by Chop Size

Chop Size	Count	Octets
1	1	1
2	1	2
4	1	4
12	1	12
169	1	169
Total	5	188

Frames Received by Opcode

Opcode	Count
8	1
Total	1

Frames Transmitted by Opcode

Opcode	Count
8	1
Total	1

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3737266167656e743d576562536f636b657470702f302e352e312d7065726d65

               73736167656465666c6174652048 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e372e ...

002 TX OCTETS: 0115

003 TX OCTETS: cebae1bdb9cf83cebcceb5f4

004 DELAY 1.000000 sec for TAG A

005 DELAY TIMEOUT on TAG A

006 TX OCTETS: 90

007 DELAY 1.000000 sec for TAG B

008 RX OCTETS: 88971f37ab991cd8e2f76956c7f07b17fecd590f8bfc7154c4fd7659cc

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

               0x03ef496e76616c6964205554463820656e636f64696e67

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

               0x03e8

011 TX OCTETS: 880203e8

012 TCP DROPPED BY ME