Working with Clusters and Match Rules
Enabling Both the Once Only and Always Options
The
always
flag influences when Equalizer inserts cookies into server responses; it in turn is
affected by the setting of the
once only
flag, as shown in the following table:
once only enabled
once only disabled
always
enabled
Equalizer always inserts a cookie into the first set
of response headers on a connection
only
. The
cookie is inserted regardless of whether the
server included one in the response.
Subsequent responses on the same connection
are forwarded to the client
unchanged
by
Equalizer.
Equalizer inserts its own cookie
into
all
server responses on a
connection. The cookie is
inserted regardless of whether
the server included one in the
response.
always
disabled
If the
first
server response on a connection
already has a server cookie in it, Equalizer
inserts its own cookie into the
first
set of
response headers on the connection. If the
response has no cookie in it, Equalizer does
not
insert one of its own.
Subsequent responses on the same connection
are forwarded to the client
unchanged
by
Equalizer.
If the
first
server response on a
connection already has a server
cookie in it, Equalizer inserts its
own cookie into the
first
set of
response headers on the
connection.
Equalizer will insert a cookie into
subsequent responses on the
same connection if:
they do not contain a valid cookie
the
cookie generation
has
changed
the server in the cookie has the
quiesce
flag enabled
Note
- the cluster parameters cookie path, cookie age, cookie generation, and cookie domain specify cookie content for
the cluster. If any of these parameters are updated, this changes the information used in the cookies that Equalizer
inserts into server responses.
Enabling Once Only and Compression
Enabling both the
once only
and
compress
options is not allowed by the GUI. These two options are
not compatible, since setting them both would mean that only the first response in a connection
would be compressed and not the remainder of the responses, which would likely cause client
errors.
Enabling Once Only and No Header Rewrite for HTTPS
In a Layer 7 HTTPS cluster, clients connect to the cluster IP using HTTPS connections. Equalizer
terminates the HTTPS connection and communicates with the server pool in the cluster using the
HTTP protocol. By default, Equalizer examines server responses for
http://
URLs and rewrites
them as
https://
URLs, so that these URLs work properly on the client. If, for example, a server
sends an HTTP redirect using the
Location:
header, this URL most likely will include the
http://
protocol. Equalizer rewrites this response so that the URL uses
https:
//.
376
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
Summary of Contents for Equalizer GX Series
Page 18: ......
Page 32: ...Overview 32 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 42: ......
Page 52: ......
Page 64: ......
Page 72: ......
Page 76: ......
Page 228: ......
Page 238: ......
Page 476: ......
Page 492: ......
Page 530: ......
Page 614: ......
Page 626: ......
Page 638: ......
Page 678: ......
Page 732: ...Using SNMP Traps 732 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 754: ......
Page 790: ......
Page 804: ......
Page 842: ......
Page 866: ......