Configuring the WSM using Device Manager

Example of SSL session ID-based persistence

The figure below illustrates the following:

1. Client 1 and Server 1 complete SSL Hello handshake through the WSM.
2. Server 1 assigns SSL session ID to Client 1.
3. The WSM records the SSL session ID.
4. The WSM selects a real server based on the existing SLB settings.

As a result, subsequent connections from Client 1 with the same SSL session ID are directed to Server 1.



5. Client 2 appears to the WSM to have the same source IP address as Client 1 because they share the same proxy firewall.

However, the WSM does not automatically direct Client 2 traffic to Server 1 based on the source IP address. Instead the server assigns a SSL session ID for the new traffic. Based on the configured SLB metric, the connection from Client 2 is spliced to Server 3. As a result, subsequent connections from Client 2 with the same SSL session ID are directed to Server 3.

See also:

• SSL session ID-based persistence
• How SSL session ID-based persistence works
• 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