Autobahn WebSocket Testsuite Report
Autobahn WebSocket

websock-secure-client - Case 13.5.2 : Pass - 381 ms @ 2024-04-24T05:50:22.845Z

Case Description

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

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=465&agent=websock-secure-client HTTP/1.1
Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=15
Upgrade: websocket
Host: 127.0.0.1:9002
Connection: Upgrade
Sec-Websocket-Version: 13
Sec-Websocket-Key: 7cDO6El9QVx8YZf8EdMvcQ==
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: vnQmuGn5eMn8Bmii2wATnHsOhzI=
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits=9


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
70100070000
2951295
Total100270303

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
74413087
81080
91431287
101741740
1136396
1268816
13781014
1428392
1516240
19119
24124
32132
37137
38138
51151
3061306
Total10029563

Frames Received by Opcode

OpcodeCount
11000
81
Total1001

Frames Transmitted by Opcode

OpcodeCount
11000
81
Total1001


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d343635266167656e743d776562736f636b2d7365637572652d636c69656e7420
               485454502f312e310d0a5365632d ...
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: 888233f44a80301c
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=3333663434613830
               0x03e8
009 TCP DROPPED BY ME