Autobahn WebSocket Testsuite Report
Autobahn WebSocket

websock-client - Case 12.5.2 : Pass - 165 ms @ 2024-11-28T05:38:57.251Z

Case Description

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

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=375&agent=websock-client HTTP/1.1
Connection: Upgrade
Upgrade: websocket
Host: 127.0.0.1:9001
Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=15
Cache-Control: no-cache
Sec-Websocket-Version: 13
Sec-Websocket-Key: WDw/f3mf8N2asTEb4cefYQ==
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: 61npwhQvlbZVRuzDCgSU8EUTH7U=
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
70100070000
2881288
Total100270296

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
7321
10220
11444
12224
13678
14228
15690
16464
176102
18354
19595
20120
21363
22122
23246
24124
25250
26252
27381
28384
29387
32396
33133
34134
35270
37137
39139
40280
42142
43143
46146
47147
502100
513153
52152
55155
56156
58158
603180
61161
622124
63163
66166
67167
683204
7290064800
2521252
Total100268011

Frames Received by Opcode

OpcodeCount
21000
81
Total1001

Frames Transmitted by Opcode

OpcodeCount
21000
81
Total1001


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d333735266167656e743d776562736f636b2d636c69656e7420485454502f312e
               310d0a436f6e6e656374696f6e3a ...
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: 8882fdfec287fe16
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=6664666563323837
               0x03e8
009 TCP DROPPED BY ME