![Coyote Point Systems E350GX Скачать руководство пользователя страница 223](http://html.mh-extra.com/html/coyote-point-systems/e350gx/e350gx_installation-and-administration-manual_2674414223.webp)
Match Functions
Equalizer Installation and Administration Guide
221
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:
Figure 48 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.
•
Match functions for the optional
<fragment>
component are not provided. The fragment portion of a URI
is not transmitted by the browser to the server, but is instead retained by the client and applied after the
reply from the server is received.
The following table lists the URI matching functions that match text in the URI components shown in Figure 48.
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.
URI Match Function
Description
host(
string
)
This function evaluates to
true
if the
string
argument exactly
matches the hostname portion of the request.
In the case of HTTP
0.9, the host is a portion of the request URI. All other HTTP protocol
versions require a Host header to specify the host, which would be
compared to the string.
non-URI Match Function
Description
Содержание E350GX
Страница 18: ...Chapter Preface 18 Equalizer Installation and Administration Guide ...
Страница 38: ...Chapter 1 Equalizer Overview 38 Equalizer Installation and Administration Guide ...
Страница 50: ...Chapter 2 Installing and Configuring Equalizer Hardware 50 Equalizer Installation and Administration Guide ...
Страница 62: ...Chapter 3 Using the Administration Interface 62 Equalizer Installation and Administration Guide ...
Страница 80: ...Chapter 4 Equalizer Network Configuration 80 Equalizer Installation and Administration Guide ...
Страница 110: ...Chapter 5 Configuring Equalizer Operation 110 Equalizer Installation and Administration Guide ...
Страница 208: ...Chapter 7 Monitoring Equalizer Operation 208 Equalizer Installation and Administration Guide ...
Страница 240: ...Chapter 8 Using Match Rules 238 Equalizer Installation and Administration Guide ...
Страница 258: ...Chapter 9 Administering GeoClusters 254 Equalizer Installation and Administration Guide Envoy Configuration Worksheet ...
Страница 262: ...Appendix A Server Agent Probes 258 Equalizer Installation and Administration Guide ...
Страница 274: ...Appendix B Timeout Configuration 270 Equalizer Installation and Administration Guide ...
Страница 280: ...Appendix D Regular Expression Format 276 Equalizer Installation and Administration Guide ...
Страница 296: ...Appendix E Using Certificates in HTTPS Clusters 292 Equalizer Installation and Administration Guide ...
Страница 310: ...Appendix F Equalizer VLB 306 Equalizer Installation and Administration Guide ...
Страница 318: ...Appendix G Troubleshooting 314 Equalizer Installation and Administration Guide ...