
tls1()
HTTPS only. This function evaluates to true if the client negotiated the
encrypted connection using TLS version 1.0.
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
associated 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.
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
All Rights Reserved.
325
Equalizer Administration Guide
Comentarios a estos manuales