Coyote Point Systems Equalizer GX Series, Administration Manual

Page: 394 / 866

Working with Clusters and Match Rules
Non-URI header match functions
See Match Bodies , for the headers that can be specified in these functions.
header_prefix(header, string)
This function evaluates to true if the selected header is present and
if the string-valued argument string is a prefix of the associated
header text.
header_suffix(header, string)
This function evaluates to true if the selected header is present and
if the argument string is a suffix of the header text.
header_substr(header, string)
This function evaluates to true if the selected header is present and
if the string-valued argument string is a sub-string of the asso-
ciated header text.
header_regex(header, string)
This function evaluates to true if the selected header is present and
if the string-valued argument string , interpreted as a regular
expression, matches the associated header text.
In addition to the functions in the preceding table, a set of functions is provided that allows you to
process requests based on the various components of a request’s destination URI.
A URI has the following parts (as defined in RFC1808):
<scheme>://<hostname>/<path>;<params>?<query>#<fragment>
In addition, Equalizer further breaks up the <path> component of the URI into the following
components:
<directory><filename>
The following figure illustrates how Equalizer breaks up a URI into the supported components:
Note that the following components of the URI do not have corresponding match functions:
l
Match functions for the <scheme> component are not necessary, since a cluster must be
configured to accept only one protocol: HTTP
or HTTPS.
l
Match functions for the optional <params> component are not provided. Use the pathname*
()
and
filename*()
functions to match characters at the end of the
path
and
filename
com-
ponents.
394 Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.