Closed sajal closed 6 years ago
Re, ssllabs: paging @ivanr for sanity check.. :-)
Thanks for pinging me :) I don't have access to the SSL Labs code any more, but I've created a ticket for this issue so that @bhushan5640 can look into it: https://github.com/ssllabs/ssllabs-scan/issues/531
SSL Labs results are correct Session resumption (caching) : No (IDs empty) Session resumption (tickets) : Yes
You can confirm with this command (use -no_ticket param to check session resumption - caching)
$ echo | openssl s_client -connect d28nqx80pet1gg.cloudfront.net:443 -reconnect -no_ticket 2> /dev/null | grep 'New\|Reuse\|Session-ID:
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Session-ID:
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Session-ID:
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Session-ID:
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Session-ID:
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Session-ID:
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Session-ID:
Woops. I was clearly mistaken.
ssllabs says
No (IDs empty)
, but testing by hand I see a session ID and can resume connections.