Page History

...

• When a client and server establish an SSL connection for the first time they need to establish ashared key called the master_secret. The master_secret is then used to create all the bulk encryption keys used to protect the traffic. The master_secret is almost invariably established using one of two public key algorithms: RSA or Diffie-Hellman (DH). Unfortunately, both of these algorithms are quite slow. In order to improve performance, SSL contains a "session resumption" feature that allows a client/server pair to skip this time consuming step if they have already established a master_secret in a previous connection. (from Eric Rescorla's article http://www.linuxjournal.com/article/5487^{Image Removed})

what's the problem in TS

• ssl session resumption can not work in some case
  • https://issues.apache.org/jira/browse/TS-718^{Image Removed}
• sessions store in ssl internal cache
  • https://issues.apache.org/jira/browse/TS-463^{Image Removed}

what we have done

...

• use http cache in TS to store ssl sesion
  • make the session_id like http request(http://ssl.session.cache/session_id^{Image Removed}) as the key
  • make the session as the value
  • use cacheProcessor API to set and get ssl session
    • use the cluster to share the session in multi-server through cacheProcessor
    • use the partition to limit the size of the cache

...