WebSocketpp/0.5.1-permessagedeflate - Case 5.11 : Pass - 1 ms @ 2015-02-27T15:15:44.331Z

Case Description

Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in octet-wise chops.

Case Expectation

The connection is failed immediately, since there is no message to continue.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

Opening Handshake

GET /runCase?case=55&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: L91dI5knt5ZL77MK7Vj3Cw== Sec-WebSocket-Version: 13 Upgrade: websocket User-Agent: WebSocketpp/0.5.1-permessagedeflate

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 RX OCTETS: 474554202f72756e436173653f636173653d3535266167656e743d576562536f636b657470702f302e352e312d7065726d65

               73736167656465666c6174652048 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e372e ...

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

               non-continuation payload

003 TX OCTETS: 80

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

               Hello, world!

005 FAIL CONNECTION AFTER 1.000000 sec

006 TX OCTETS: 18

007 TX OCTETS: 6e

008 TX OCTETS: 6f

009 RX OCTETS: 889e22f97da7211334c9549811ce46d910c2518a1cc047d91ec84c8d14c9579809ce4d97

010 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=30, MASKED=True, MASK=3232663937646137

               0x03ea496e76616c6964206d65737361676520636f6e74696e756174696f6e

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

               0x03e8

012 TCP DROPPED BY ME

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	1002	The close code the peer sent me in close frame (if any).
remoteCloseReason	Invalid message continuation	The close reason the peer sent me in close frame (if any).

Chop Size	Count	Octets
1	4	4
169	1	169
Total	5	173