Autobahn WebSocket Testsuite Report
Autobahn WebSocket

websock secure server - Case 12.5.3 : Pass - 231 ms @ 2024-11-28T05:36:47.579Z

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 /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: 8EeMzvVRkJKT1nMljePx4A==
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Date: Thu, 28 Nov 2024 05:36:47 GMT
Sec-Websocket-Extensions: permessage-deflate; client_no_context_takeover
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Accept: T4aG43VPG19qdlNnxQG4CU2Bcjc=

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
2401240
2601000260000
Total1002260244

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
1361136
1432286
1571157
1581158
1691169
1701170
1711171
1721172
1732346
1761176
1782356
1831183
1841184
1851185
1881188
1901190
1932386
1972394
2002400
2012402
2021202
2031203
2041204
2051205
2061206
2071207
2114844
2131213
2152430
2181218
2191219
2202440
2214884
2221222
2231223
2242448
2253675
2261226
2271227
2282456
2291229
2301230
2311231
2321232
2332466
2341234
2361236
2372474
2381238
2391239
2402480
2411241
2421242
2451245
2461246
2472494
2481248
2491249
2521252
2533759
2571257
2582516
2591259
2601260
2612522
2623786
2632526
2661266
2671267
2681268
270900243000
3411341
Total1002265302

Frames Received by Opcode

OpcodeCount
21000
81
Total1001

Frames Transmitted by Opcode

OpcodeCount
21000
81
Total1001

Wire Log

000 TX OCTETS: 474554202f77737320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f30
               2e382e322d302e31302e390d0a48 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205468752c203238204e6f
               7620323032342030353a33363a34 ...
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=2f52559d, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
006 TX OCTETS: 88822f52559d2cba
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