Case Description

Send small text message, then send again with RSV = 4, then send Ping. Octets are sent in octet-wise chops.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since RSV must be 0, when no extension defining RSV meaning has been negotiated. The Pong is not received.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': [('message', u'Hello, world!', False)], 'NON-STRICT': []}

Observed:
[('message', u'Hello, world!', False)]

Case Closing Behavior

The close code should have been 1002 or empty (WRONG CODE)

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

               6c6f63616c686f73743a39303032 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

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

               Hello, world!

003 TX OCTETS: 81

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

               Hello, world!

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

006 FAIL CONNECTION AFTER 1.000000 sec

007 TX OCTETS: 0d

008 TX OCTETS: 48

009 TX OCTETS: 65

010 TX OCTETS: 6c

011 TX OCTETS: 6c

012 TX OCTETS: 6f

013 TX OCTETS: 2c

014 TX OCTETS: 20

015 TX OCTETS: 77

016 TX OCTETS: 6f

017 TX OCTETS: 72

018 TX OCTETS: 6c

019 TX OCTETS: 64

020 TX OCTETS: 21

021 TX OCTETS: c1

022 RX OCTETS: 818d08ddaecd40b8c2a167f18eba67afc2a929

023 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASKED=True, MASK=3038646461656364

               Hello, world!

024 TX OCTETS: 0d

025 TX OCTETS: 48

026 TX OCTETS: 65

027 RX OCTETS: 889b1690a7fa1560ce9460f1cb9372b0cb9f77f4ce9471b0c59362e387cb27a097889bbb08fd1cb8f89472cd699175df2891

               79da6c9472dc289f75cf7bdd2d8a ...

028 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=27, MASKED=True, MASK=3136393061376661

               0x03f0696e76616c6964206c656164696e6720626974732031313030

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

               0x03e8

030 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 WebSocket 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	1008	The close code the peer sent me in close frame (if any).
remoteCloseReason	invalid leading bits 1100	The close reason the peer sent me in close frame (if any).

Chop Size	Count	Octets
19	1	19
181	1	181
2046	1	2046
Total	3	2246