Hi,
Looking at the output of 'show info' on stats socket I see
[...snip...]
SslFrontendKeyRate: 0
SslFrontendMaxKeyRate: 31
SslFrontendSessionReuse_pct: 100
SslBackendKeyRate: 0
SslBackendMaxKeyRate: 6
SslCacheLookups: 698093
SslCacheMisses: 417817
[...snip...]
Would it be an accurate measurement of SSL Cache hits if I do
SslCacheLookups minus SslCacheMisses?
In our our setup we use Session IDs and TLS session ticketing, see below,
so I assume that Cache counter will be used for both.
openssl s_client -connect foo.bar.com:443 -tls1 -tlsextdebug -status
[...snip...]
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-SHA
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
Protocol : TLSv1
Cipher : ECDHE-RSA-AES256-SHA
Session-ID:
3125F0852942082B52942BC0F432F7FFCFAFB540F23EB0E57CBDC1135728F0AF
Session-ID-ctx:
Master-Key:
27A9699E9F72831E2BA2D66BB59044A47FD91C55A1CC7A82715B5A8A290BE1E007C477A0EC0193D5C869FDED6F49B646
Key-Arg : None
Krb5 Principal: None
PSK identity: None
PSK identity hint: None
TLS session ticket lifetime hint: 300 (seconds)
TLS session ticket:
0000 - f1 d1 d3 e1 dd c0 3d 83-d9 1e c0 89 df c5 f5 9b
......=.........
[...snip...]
what does the SslFrontendSessionReuse_pct measure ? I failed to find any
info about it in docs/Internet, I haven't checked the code yet:-)
Cheers,
Pavlos
