Specifications

Chapter 8: Working with Match Rules
138 Equalizer Installation and Administration Guide
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.
5. 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, with one exception: currently the “-” (dash) character in URIs is not
matched by the host*() functions. The workaround is to use the header*() functions instead to
match on the Host header. Also note 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).
Logical Operators and Constructs in the GUI
In addition to the Match Functions listed in the previous section, the Equalizer Administrative
Interface provides the following logical operators and constructs that allow you to combine the
match functions into logical expressions, and manipulate the functions in the match expression. All
of these operators and constructs affect the part of the match expression that is currently selected
(highlighted in red) in the graphical interface.
Note – Given that HTTPS runs encrypted using SSL and TLS as the transport, in order to
perform any Layer 7 processing, the Equalizer must terminate the SSL/TLS encrypted
connection. This can have deleterious effects on performance, as the encryption and
decryption process is resource-intensive. A hardware accelerator, Xcel, is available which
can be added to the Equalizer platform to ameliorate this problem.
Table 65: Match Rule Logical Operators and Constructs
negate function This function negates (or reverses) the value of the expression
that comes immediately after it in the match definition. When
using the GUI to construct a match rule, choosing this function
negates the currently selected function in the match rule
expression and appears on screen as the string “NOT”. In the
eq.conf file, it negates the function immediately following it and
appears as an exclamation point (!).
delete selection Removes the currently selected portion of the match expression.
replace with AND Replaces the currently selected logical operator with “AND”.
replace with OR Replaces the currently selected logical operator with “OR”.
replace with any AND any Replaces the currently selected logical construct with “any() AND
any()”.
replace with any OR any Replaces the currently selected logical construct with “any() OR
any()”.
replace with self AND any Replaces the currently selected logical construct with the current
selection logically AND’ed with the “any()” function.
replace with self OR any Replaces the currently selected logical construct with the current
selection logically OR’ed with the “any()” function.
replace with any AND self Replaces the currently selected function or logical construct with
the “any()” function logically AND’ed with the current selection.
replace with any OR self Replaces the currently selected function or logical construct with
the “any()” function logically OR’ed with the current selection.