9-2
User
Guide
for
the
Cisco
Application
Networking
Manager
5.2
OL-26572-01
Chapte
r
9
Configuring
Stickiness
Sticky
Types
Stickiness
allows
the
same
client
to
maintain
multiple
simultaneous
or
subsequent
TCP
or
IP
connections
with
the
same
real
server
for
the
duration
of
a
session.
A
session
is
series
of
transactions
between
a
client
and
a
server
over
some
finite
period
of
time
(from
several
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
and
during
the
checkout
process.
Depending
on
the
configured
SLB
policy,
the
ACE
sticks
a
client
to
an
appropriate
server
after
the
ACE
has
determined
which
load-balancing
method
to
use.
If
the
ACE
determines
that
a
client
is
already
stuck
to
a
particular
server,
then
the
ACE
sends
that
client
request
to
that
server,
regardless
of
the
load-balancing
criteria
specified
by
the
matched
policy.
If
the
ACE
determines
that
the
client
is
not
stuck
to
a
particular
server,
it
applies
the
normal
load-balancing
rules
to
the
content
request.
For
information
about
stickiness,
see
the
following
topics:
•
Sticky
Types,
page
9-2
•
Sticky
Groups,
page
9-6
•
Sticky
Table,
page
9-6
Related
Topics
•
Configuring
Virtual
Server
Default
Layer
7
Load
Balancing,
page
7-50
•
Configuring
Sticky
Groups,
page
9-7
Sticky
Types
All
ACE
devices
support
stickiness
based
on
the
following:
•
HTTP
cookies
•
HTTP
headers
•
IP
addresses
•
HTTP
content
•
Layer
4
pa
yloads
•
RADIUS
attributes
•
RTSP
headers
•
SIP
headers
This
section
includes
the
following
topics:
•
HTTP
Content
Stickiness,
page
9-3
•
HTTP
Cookie
Stickiness,
page
9-3
•
HTTP
Header
Stickiness,
page
9-4
•
IP
Netmask
and
IPv6
Prefix
Stickiness,
page
9-4
•
Layer
4
Payload
Stickiness,
page
9-4
•
RADIUS
Stickiness,
page
9-5
•
RTSP
Header
Stickiness,
page
9-5
•
SIP
Header
Stickiness,
page
9-5
