Case Description

Send small text message, then send frame with reserved control Opcode = 15 and non-empty payload, then send Ping.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A 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: 474554202f72756e436173653f636173653d3434266167656e743d636c69656e7420485454502f312e310d0a486f73743a20

               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=15, FIN=True, RSV=0, 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: 8f

022 TX OCTETS: 0d

023 RX OCTETS: 818d32b1f8347ad494585d9dd8435dc3945013

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

               Hello, world!

025 TX OCTETS: 48

026 TX OCTETS: 65

027 TX OCTETS: 6c

028 TX OCTETS: 6c

029 TX OCTETS: 6f

030 TX OCTETS: 2c

031 TX OCTETS: 20

032 TX OCTETS: 77

033 TX OCTETS: 6f

034 TX OCTETS: 72

035 TX OCTETS: 6c

036 TX OCTETS: 64

037 TX OCTETS: 21

038 TX OCTETS: 89

039 TX OCTETS: 00

040 RX OCTETS: 88828a5b2d0a89b3

041 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=3861356232643061

               0x03e8

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

               0x03e8

043 TX OCTETS: 880203e8

044 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	1000	The close code the peer sent me in close frame (if any).
remoteCloseReason	None	The close reason the peer sent me in close frame (if any).

Chop Size	Count	Octets
8	1	8
19	1	19
181	1	181
Total	3	208