websock secure server - Case 2.3 : Pass - 11 ms @ 2024-11-28T05:30:34.658Z

Case Description

Send ping with small binary (non UTF-8) payload.

Case Expectation

Pong with payload echo'ed is sent in reply to Ping. Clean close with normal code.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': [('pong', '0x00fffefdfcfb00ff')]}

Observed:
[('pong', '0x00fffefdfcfb00ff')]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET /wss HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: 127.0.0.1:8889
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: kZWsT3PAtJc9nRlxV33/Vw==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Date: Thu, 28 Nov 2024 05:30:34 GMT
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Accept: EtZNB8sUiBQdhkiuKpFcHIctyHw=

Closing Behavior

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 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).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
4	1	4
10	1	10
166	1	166
Total	3	180

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
14	1	14
243	1	243
Total	3	265

Frames Received by Opcode

Opcode	Count
8	1
10	1
Total	2

Frames Transmitted by Opcode

Opcode	Count
8	1
9	1
Total	2

Wire Log

000 TX OCTETS: 474554202f77737320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f30

               2e382e322d302e31302e390d0a48 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205468752c203238204e6f

               7620323032342030353a33303a33 ...

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

               0x00fffefdfcfb00ff

003 TX OCTETS: 8988b1733418b18ccae54d8834e7

004 CLOSE CONNECTION AFTER 1.000000 sec

005 RX OCTETS: 8a0800fffefdfcfb00ff

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

               0x00fffefdfcfb00ff

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

               0x03e8

008 TX OCTETS: 8882b02a85a3b3c2

009 RX OCTETS: 880203e8

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

               0x03e8

011 TCP DROPPED BY PEER