Specifications

Chapter 8: Working with Match Rules

134 Equalizer Installation and Administration Guide

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):

In addition, Equalizer further breaks up the <path> component of the URI into the following

components:

The following figure illustrates how Equalizer breaks up a URI into the supported components:

Figure62 URI components

Note that the following components of the URI do not have corresponding match functions:

• Match functions for the <scheme> component are not necessary, since a cluster must be

configured to accept only one protocol: HTTP or HTTPS.

• 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 components.

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.

ssl2() HTTPS only. This function evaluates to true if the client

negotiated the encrypted connection using SSL version 2.0.

ssl3() HTTPS only. This function evaluates to true if the client

negotiated the encrypted connection using SSL version 3.0.

tls1() HTTPS only. This function evaluates to true if the client

negotiated the encrypted connection using TLS version 1.0.

Table 61: non-URI Match Functions

non-URI Match Function Description