
Accept-Language If-Modified-Since Transfer-Encoding
Authorization If-None-Match Upgrade
Cache-Control If-Range User-Agent
Connection If-Unmodified-Since Via
Content-Length Max-Forwards Warning
Cookie Pragma X-Forwarded-For
Date Proxy-Authorization
Expect Range
HTTPS Protocol Matching
Equalizer permits the construction of virtual clusters running the HTTPS protocol. HTTPS is HTTP running over an encrypted
transport, typically SSL version 2.0 or 3.0 or TLS version 1.0. All of the functions available for load balancing HTTP clusters
are available for HTTPS clusters. In addition, there are some additional match functions [ssl2(), ssl3(), and tls1()], that match
against the protocol specified in an HTTPS request.
Supported Characters in URIs
The characters permitted in a URI are defined in RFC2396. Equalizer supports all characters defined in the
standard for all Match Functions that have a URI as an argument. Note in particular that the ASCII space
character is not permitted in URIs -- it is required to be encoded by all conforming browsers as “%20” (see Section
2.4 of RFC2396).
Match Rules, the Once Only Flag, and Cookies
Since multiple client requests may be received on a single TCP/IP connection, Equalizer has a flag (once only)
that specifies whether to check the headers in every request received on a connection, or to load balance based
solely The once only flag is a cluster parameter on the Networking tab. When using Match Rules, it is usually
desirable to turn off the once only flag for the cluster so that Equalizer matches against each individual request in
a connection, not just the first one.
You can also enable or disable once only flag in the match rule Configuration screen (tab), to override the setting
on the cluster for any request that matches that rule. For example, if once only is enabled on a cluster and
disabled on a match rule, any request that matches that match rule’s expression will be load balanced as if once
only were disabled on the cluster.
The following table shows how the setting of once only affects load balancing when a match rule hit occurs:
match rule hit on... once only disabled once only enabled
...the first request on
a connection
If the request headerscontain a cookie
specifying a server in the match rule’s server list,
send the request to the server in the cookie.
Otherwise, send the request to the server in the
match rule’s server list that is selected by the
load balancing policyin effect for the match rule.
Same as at left.
...second and
subsequent requests
Same as above.
If the request headerscontain a cookie
specifying a server in the match rule’s server
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
All Rights Reserved.
331
Equalizer Administration Guide
Kommentare zu diesen Handbüchern