This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients giampaolo.rodola, janssen, jcea, pitrou
Date 2010-10-12.17:15:37
SpamBayes Score 0.03079916
Marked as misclassified No
Message-id <1286903739.39.0.265190356323.issue8106@psf.upfronthosting.co.za>
In-reply-to
Content
http://www.openssl.org/docs/ssl/SSL_CTX_set_session_cache_mode.html suggests that SSL session caching already occurs by default in server mode:

“SSL_SESS_CACHE_SERVER

    Server sessions are added to the session cache. When a client proposes a session to be reused, the server looks for the corresponding session in (first) the internal session cache (unless SSL_SESS_CACHE_NO_INTERNAL_LOOKUP is set), then (second) in the external cache if available. If the session is found, the server will try to reuse the session. This is the default.”


A nice and easy thing to do would be to export the statistics given by http://www.openssl.org/docs/ssl/SSL_CTX_sess_number.html# .
History
Date User Action Args
2010-10-12 17:15:39pitrousetrecipients: + pitrou, jcea, janssen, giampaolo.rodola
2010-10-12 17:15:39pitrousetmessageid: <1286903739.39.0.265190356323.issue8106@psf.upfronthosting.co.za>
2010-10-12 17:15:37pitroulinkissue8106 messages
2010-10-12 17:15:37pitroucreate