websock-secure-client - Case 4.1.3 : Pass - 1 ms @ 2024-04-24T05:20:17.845Z

Case Description

Send small text message, then send frame with reserved non-control Opcode = 5, 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:
{'NON-STRICT': [], 'OK': [('message', u'Hello, world!', False)]}

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

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET /runCase?case=37&agent=websock-secure-client HTTP/1.1
Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=15
Upgrade: websocket
Host: 127.0.0.1:9002
Connection: Upgrade
Sec-Websocket-Version: 13
Sec-Websocket-Key: q7EXndUWxDCbAlNWNQuG2A==
Cache-Control: no-cache

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

Closing Behavior

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	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
19	1	19
294	1	294
Total	2	313

Octets Transmitted by Chop Size

Chop Size	Count	Octets
2	2	4
15	1	15
206	1	206
Total	4	225

Frames Received by Opcode

Opcode	Count
1	1
Total	1

Frames Transmitted by Opcode

Opcode	Count
1	1
5	1
9	1
Total	3

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3337266167656e743d776562736f636b2d7365637572652d636c69656e742048

               5454502f312e310d0a5365632d57 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

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

               Hello, world!

003 TX OCTETS: 810d48656c6c6f2c20776f726c6421

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

005 TX OCTETS: 8500

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

007 TX OCTETS: 8900

008 FAIL CONNECTION AFTER 1.000000 sec

009 RX OCTETS: 818d3abc474a72d92b265590673d55ce2b2e1b

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

               Hello, world!

011 TCP DROPPED BY PEER