AutobahnPython/0.10.9 - Case 3.3 : Non-Strict - 1 ms @ 2021-07-17T23:53:16.322Z

Case Description

Send small text message, then send again with RSV = 3, then send Ping. Octets are sent in frame-wise chops. 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:
{'NON-STRICT': [], 'OK': [('message', u'Hello, world!', False)]}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.1-0.10.9
Host: 127.0.0.1:9001
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: ENPkP2c2nWbZdSjBJ+8HVA==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Server: AutobahnPython/0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: P4iR63QBeya9AaQYrxjLa0oxBho=

Closing Behavior

Key	Value	Description
isServer	False	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	False	True, iff I dropped the TCP connection.
wasClean	False	True, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReason	peer dropped the TCP connection without previous WebSocket closing handshake	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	None	The close code I sent in close frame (if any).
localCloseReason	None	The close reason I sent in close frame (if any).
remoteCloseCode	None	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).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
197	1	197
Total	1	197

Octets Transmitted by Chop Size

Chop Size	Count	Octets
6	1	6
19	2	38
240	1	240
Total	4	284

Frames Received by Opcode

Opcode	Count
Total	0

Frames Transmitted by Opcode

Opcode	Count
1	2
9	1
Total	3

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e

               312d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               507974686f6e2f302e31302e390d ...

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

               Hello, world!

003 TX OCTETS: 818d037624e84b1348846c5a049f6c04488c22

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

               Hello, world!

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

006 FAIL CONNECTION AFTER 1.000000 sec

007 TX OCTETS: b18d28d6a12360b3cd4f47fa815447a4cd4709

008 TX OCTETS: 898043bb6299

009 TCP DROPPED BY PEER