Specifications

Working with Virtual Clusters
Equalizer Installation and Administration Guide 71
will only present the cookie to servers in the coyotepoint.com domain (for example,
www.coyotepoint.com or my.coyotepoint.com).
• cookie path presents the cookie only when the path component of the request URI has
the same prefix as that of the specified path. For example, if the cookie path is
/store/,
the browser presents the cookie only if the request URI includes a path such as
/store/mypage.html.
• always includes a cookie in the response whether or not the server actually set a cookie.
If this flag is not enabled, Equalizer only sends a persistence cookie when the server
sends a cookie of its own.
12. For HTTPS clusters, choose from the following options:
• x509 verify has Equalizer check that the certificate meets the X.509 standard when you
upload a certificate. Certain self-signed or chained certificates will not pass this
verification and in that instance, you will want to disable the test. To see this flag, check
the advanced flag.
• dont munge forces Equalizer to pass responses from the cluster’s servers without
rewriting them. In the typical Equalizer setup, you configure the servers in an HTTPS
cluster to listen and respond using HTTP; Equalizer communicates with the clients using
SSL. If a server sends an HTTP redirect using the Location: header, this URL most likely
will not include the
https: protocol. Equalizer rewrites (munges) responses from the
server so that they are HTTPS. You can direct Equalizer pass responses from the server
without rewriting them by enabling the dont munge flag.
13. For L4 TCP and L4 UDP clusters, choose from the following options:
• sticky time is the number of seconds that Equalizer should “remember” connections from
clients. If you don't need sticky connections, set this option to 0. For more information,
refer to “Enabling Sticky Connections” on page 80.
• intercluster sticky is an option that when enabled ensures that Equalizer directs requests
from a particular user to the same server, even if the connection is to a different virtual
cluster. For more information, refer to “Enabling Sticky Connections” on page 80.
• probe ssl (L4 TCP only) causes Equalizer to use SSL when it sends the ACV probe
string. For more information, refer to “Using Active Content Verification (ACV)” on
page 83.
14. Click the commit button to add the virtual cluster.
Equalizer can refuse an Add Cluster command for several reasons, including:
• Attempting to add a cluster address that is already configured or is configured as a server
address
• Specifying an invalid cluster names
• Specifying an invalid IP address or port number
• Attempting to add more clusters than are supported by Equalizer
Advanced Cluster Fields and Flags
When you check the advanced flag check box at the bottom of the add cluster or modify cluster
screens, additional fields are displayed. For most operations the default values are acceptable. The
modifiable fields are described below: