7-2
Device Manager Guide, Cisco ACE 4700 Series Application Control Engine Appliance
OL-26645-02
Chapter 7 Configuring Stickiness
Stickiness Overview
minutes to several hours). This feature is particularly useful for e-commerce applications where a client
needs to maintain multiple connections with the same server while shopping online, especially while
building a shopping cart using HTTP requests and during the checkout process using HTTPS.
Depending on the configured SLB policy, the ACE appliance “sticks” a client to an appropriate server
after the ACE appliance has determined which load-balancing method to use. If the ACE appliance
determines that a client is already stuck to a particular server, then the ACE appliance sends that client
request to that server, regardless of the load-balancing criteria specified by the matched policy. If the
ACE appliance determines that the client is not stuck to a particular server, it applies the normal
load-balancing rules to the content request.
You can configure stickiness to stick a client to a real server that is associated with a server farm or you
can use the buddy sticky group feature to enable persistence to a real server or real server group across
multiple server farms (see the “Buddy Sticky Groups” section on page 7-6).
For overview information on stickiness, see the following topics:
• Sticky Types
• Sticky Groups
• Sticky Table
• Buddy Sticky Groups
Related Topics
• Configuring Virtual Server Layer 7 Load Balancing, page 5-30
• Configuring Sticky Groups, page 7-11
Sticky Types
The ACE appliance supports stickiness based on:
• HTTP cookies
• HTTP headers
• IP addresses
• HTTP content
• IP Netmask
• IPv6 Prefix
• Layer 4 payloads
• RADIUS attributes
• RTSP headers
• SIP headers
• SSL session ID
Related Topics
• HTTP Content Stickiness, page 7-3
• HTTP Cookie Stickiness, page 7-3
• HTTP Header Stickiness, page 7-4
• IP Netmask and IPv6 Prefix Stickiness, page 7-4
Comments to this Manuals