Aiyappa,
If an application requires that a user be stuck for the entire session, use Layer 3 sticky, which sticks a user to a server based on the user's IP address.
If a large percentage of your customers come to you through a mega-proxy, then consider using a different sticky method (for example, the
advanced-balance method cookies, and cookieurl url).
Example:
Owner sticky
content sticky-cookie
vip address 192.10.10.1
url ?/*?
advanced-balance cookie
add service server1
add service server2
active
service server1
ip address 10.0.3.221
string server1
active
service server2
ip address 10.0.3.222
string server2
active
The cookie is entered by using the 'string' command.
The service is then added to the Content Rule.
Enables the content rule to stick the client to the server based on the configured string found in the HTTP cookie header. You must specify a port in the content rule to use this option. The CSS will then spoof the connection. A content rule with a sticky configuration set to advanced-balance cookies requires all clients to enable cookies on their browser.
When a client makes an initial request, they do not have a cookie. But once they go to a server that is capable of setting cookies, they receive the cookie from the server. Each subsequent request contains the cookie until the cookie expires. A string in a cookie can be used to stick a client to a server. The service mode string command enables you to specify where the CSS should locate the string within the cookie.
Hope this will help you out.
thanks
