WebSocket++/0.5.1-permessagedeflate - Case 7.3.6 : Pass - 1 ms @ 2015-02-27T15:42:05.800Z

Case Description

Send a close frame with close code and close reason which is too long (124) - total frame payload 126 octets

Case Expectation

Clean close with protocol error code or dropped TCP connection.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

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: ur5UolWEO2DRULn9qMDmXw== 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: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e

               312d302e31302e300d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2075706772

               6164650d0a5365632d576562536f ...

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

               0x03e82a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a

               2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a ...

003 TX OCTETS: 88fe007edd1a01c5def22beff7302beff7302beff7302beff7302beff7302beff7302beff7302beff7302beff7302beff730

               2beff7302beff7302beff7302bef ...

004 FAIL CONNECTION AFTER 1.000000 sec

005 RX OCTETS: 883b03ea436f6e74726f6c206d6573736167657320617265206c696d6974656420746f206665776572207468616e20313235

               2063686172616374657273 ...

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

               0x03ea436f6e74726f6c206d6573736167657320617265206c696d6974656420746f206665776572207468616e2031323520

               63686172616374657273

007 TCP DROPPED BY PEER

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	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	****************************************************************************************************************************	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	Control messages are limited to fewer than 125 characters	The close reason the peer sent me in close frame (if any).

Chop Size	Count	Octets
134	1	134
240	1	240
Total	2	374