Coyote Point Systems Equalizer GX Series, Administration Manual

Page: 401 / 866

Supported Headers
All of the
header_*
match functions take a
header
argument, which selects the header of interest. If
this header is not present in the request, the match function evaluates to false .
Although HTTP permits a header to span multiple request lines, none of the functions match text
on more than one line. In addition, Equalizer will only parse the first instance of a header. If, for
example, a request has multiple
cookie headers, Equalizer will only match against the first cookie
header in the request.
Any text that you enter will be accepted as the header text.
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).
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
All Rights Reserved. 401
Equalizer Administration Guide