URI affinity | Server affinity conclusion


Load Balancer: SSL session ID


During establishment of an SSL encrypted session, a handshake protocol is used to negotiate a session ID. This handshaking phase consumes a good deal of CPU power, so directing subsequent HTTPS requests to the same server, using the already established SSL session, saves processing time and increases the overall performance of the Web server.

Load Balancer watches the packets during the handshake phase and holds information about the session ID if SSL session negotiation is detected. To avoid repeated SSL handshakes between a client and different Web servers, this affinity type may be configured for WebSphere Commerce.

The forwarding method used to configure SSL session ID affinity is the Dispatcher's CBR forwarding method.