Autobahn WebSocket Testsuite Report
Autobahn WebSocket

wtx - Case 13.1.2 : Pass - 180 ms @ 2023-09-27T21:07:22.724Z

Case Description

Send 1000 compressed messages each of payload size 64, auto-fragment to 0 octets. Use permessage-deflate client offers (requestNoContextTakeover, requestMaxWindowBits): [(False, 0)]

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 /runCase?case=393&agent=wtx HTTP/1.1
Connection: Upgrade
Host: 127.0.0.1:9080
Sec-WebSocket-Key: AP0Gx0JW3Pakkm1yv1TSUg==
Sec-WebSocket-Version: 13
Upgrade: websocket
Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=12; server_max_window_bits=12; client_no_context_takeover; server_no_context_takeover
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: xaYTiCKn+xxtjlJSfQnVGywmpCU=
Sec-WebSocket-Extensions: permessage-deflate; server_no_context_takeover; server_max_window_bits=12


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
395195
4022880
415205
42331386
4316688
447308
4513585
4614644
4715705
485240
49653185
50542700
51231173
52502600
53633339
54935022
557385
561739688
5713741
58291682
59181062
605300
615305
631499387
649576
657455
66654290
674268
687476
69241656
702140
3351335
Total100255609

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
355175
368288
37311147
38351330
3911429
4015600
4117697
4220840
4322946
44562464
45542430
4616736
47502350
48763648
49834067
50844200
51613111
52402080
53211113
5411594
5516880
5611616
57301710
58895162
59684012
60362160
6114854
6215930
635315
3071307
Total100250195

Frames Received by Opcode

OpcodeCount
11000
81
Total1001

Frames Transmitted by Opcode

OpcodeCount
11000
81
Total1001


Wire Log

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