websock server - Case 9.8.4 : Pass - 129 ms @ 2024-11-28T05:31:09.636Z

Case Description

Send 1000 binary messages of payload size 256 to measure implementation/network RTT (round trip time) / latency.

Case Expectation

Receive echo'ed binary messages (with payload as sent). Timeout case after 120 secs.

Case Outcome

Ok, received all echo'ed messages in time.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET /ws HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: 127.0.0.1:8888
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: THeMiAu34sbskrUDc25yLA==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Date: Thu, 28 Nov 2024 05:31:09 GMT
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Accept: FEYF5N9CzEkdlnKdEq2uBtpDEvA=

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
166	1	166
260	1000	260000
Total	1002	260170

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
242	1	242
264	1000	264000
Total	1002	264250

Frames Received by Opcode

Opcode	Count
2	1000
8	1
Total	1001

Frames Transmitted by Opcode

Opcode	Count
2	1000
8	1
Total	1001

Wire Log

000 TX OCTETS: 474554202f777320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e

               382e322d302e31302e390d0a486f ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205468752c203238204e6f

               7620323032342030353a33313a30 ...

002 WIRELOG DISABLED

003 CLOSE CONNECTION AFTER 120.000000 sec

004 WIRELOG ENABLED

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

               0x03e8

006 TX OCTETS: 88826c3f95906fd7

007 RX OCTETS: 880203e8

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

               0x03e8

009 TCP DROPPED BY PEER