Configuring the WSM using Device Manager

SSL session ID-based persistence

Secure sockets layer (SSL) is a set of protocols built on top of TCP/IP that allows an application server and client to communicate over an encrypted HTTP session, providing authentication, non-repudiation, and security. The client and server complete the SSL protocol handshake using clear (unencrypted) text. The content data is then encrypted (using an algorithm exchanged during the handshake) prior to being transmitted.

Using the SSL session ID, the WSM forwards the client request to the same real server to which it was bound during the last session. Because SSL protocol allows many TCP connections to use the same session ID from the same client to a server, key exchange needs to be done only when the session ID expires. This reduces server overhead and provides a mechanism, even when the client IP address changes, to send all sessions to the same real server.

Note: You can configure the destination port number to monitor for SSL traffic.

See also:

• How SSL session ID-based persistence works
• Example of SSL session ID-based persistence
• Examples of cookie values
• About session persistence
• About cookie-based persistence
• Handling client browsers that do not accept cookies
• Configuring cookie-based session persistence
• Configuring SSL session ID-based persistence