Autobahn WebSocket Testsuite Report
Autobahn WebSocket

ws@8.17.0 - Case 12.3.2 : Pass - 484 ms @ 2024-05-17T18:03:17.708Z

Case Description

Send 1000 compressed messages each of payload size 64, auto-fragment to 0 octets. Use default permessage-deflate offer.

Case Expectation

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

Case Outcome

Ok, received all echo'ed messages in time.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: 192.168.0.103:9002
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: KYlwkYTpZYkn1s+UvioVWQ==
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: Y+Yv8QnNvJRfCuGxxq3vwCiG3kk=
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover


Closing Behavior

KeyValueDescription
isServerFalseTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeTrueTrue, iff I have initiated closing handshake (that is, did send close first).
failedByMeFalseTrue, 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.
droppedByMeFalseTrue, iff I dropped the TCP connection.
wasCleanTrueTrue, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonNoneWhen wasClean == False, the reason what happened.
wasServerConnectionDropTimeoutFalseWhen we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeoutFalseWhen performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeoutFalseWhen we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode1000The close code I sent in close frame (if any).
localCloseReasonNoneThe close reason I sent in close frame (if any).
remoteCloseCode1000The close code the peer sent me in close frame (if any).
remoteCloseReasonNoneThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
414
14228
15230
17117
18118
19119
20120
21121
22244
24248
256150
26126
279243
2816448
2919551
3026780
3127837
32521664
33622046
34872958
35722520
36903240
371053885
38873306
39692691
40582320
41481968
42371554
43331419
4421924
4515675
469414
4710470
488384
49298
50150
514204
522104
53153
54154
55155
56156
57157
58158
59159
60160
62162
64164
67167
2031203
Total100237026

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
47147
52152
54154
553165
574228
582116
595295
604240
616366
6213806
6310630
64211344
65422730
66674422
67895963
681359180
6918312627
7020514350
7115110721
72412952
73161168
3421342
Total100268806

Frames Received by Opcode

OpcodeCount
21000
81
Total1001

Frames Transmitted by Opcode

OpcodeCount
21000
81
Total1001


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
               322d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a436f6e6e656374696f6e ...
002 WIRELOG DISABLED
003 CLOSE CONNECTION AFTER 60.000000 sec
004 WIRELOG ENABLED
005 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=c82fe72a, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
006 TX OCTETS: 8882c82fe72acbc7
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