Autobahn WebSocket Testsuite Report
Autobahn WebSocket

websock-client - Case 12.2.3 : Pass - 158 ms @ 2024-04-24T05:21:15.748Z

Case Description

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

Case Expectation

Receive echo'ed 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 /runCase?case=322&agent=websock-client HTTP/1.1
Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=15
Upgrade: websocket
Host: 127.0.0.1:9001
Connection: Upgrade
Sec-Websocket-Version: 13
Sec-Websocket-Key: VKof44MZm9xRqKQMCyyCqA==
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: BdC12OLiOp97welezcNpThRw2G4=
Sec-WebSocket-Extensions: permessage-deflate

Closing Behavior

KeyValueDescription
isServerTrueTrue, 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.
droppedByMeTrueTrue, 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
818
2641000264000
2881288
Total1002264296

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
717
68168
1861186
2052410
2072414
2081208
2121212
2131213
2152430
2164864
2172434
21851090
2203660
2214884
22251110
2231223
2242448
2252450
2264904
2272454
22861368
2291229
2302460
23151155
2323696
2334932
2344936
2361236
2372474
2382476
239102390
24061440
241102410
242174114
243245832
244225368
245204900
246276642
247286916
248276696
2494711703
2504711750
2515513805
2525112852
2534711891
2544411176
2554711985
2564611776
2575514135
2585714706
2594110619
2605013000
261369396
262379694
263246312
26461584
2664411704
Total1002251431

Frames Received by Opcode

OpcodeCount
21000
81
Total1001

Frames Transmitted by Opcode

OpcodeCount
21000
81
Total1001

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d333232266167656e743d776562736f636b2d636c69656e7420485454502f312e
               310d0a5365632d576562736f636b ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
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=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
006 TX OCTETS: 880203e8
007 RX OCTETS: 88824b866b27486e
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=3462383636623237
               0x03e8
009 TCP DROPPED BY ME