Autobahn WebSocket Testsuite Report
Autobahn WebSocket

websock server - Case 12.2.3 : Pass - 186 ms @ 2024-11-28T05:31:46.122Z

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 /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: aaAeY0fT5VOzeAY9HIh8NA==
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:31:46 GMT
Sec-Websocket-Extensions: permessage-deflate; client_no_context_takeover
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Accept: l+1ZUWTWh6NNLsRGbZpIeOyc1Ck=


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
1901190
2091209
2112422
2332466
2341234
23571645
23651180
23761422
2381238
2393717
2404960
2411241
2423726
2432486
2442488
2452490
2464984
2474988
24851240
24951245
2503750
2513753
25241008
2532506
254133302
25582040
256102560
257102570
25861548
259112849
260123120
261123132
262123144
263297627
264195016
265256625
266225852
267338811
268225896
270683184410
3401340
Total1002266438

Frames Received by Opcode

OpcodeCount
21000
81
Total1001

Frames Transmitted by Opcode

OpcodeCount
21000
81
Total1001


Wire Log

000 TX OCTETS: 474554202f777320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e
               382e322d302e31302e390d0a486f ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205468752c203238204e6f
               7620323032342030353a33313a34 ...
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=9768ded1, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
006 TX OCTETS: 88829768ded19480
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