Automatic Cluster Responders
5. On the next screen, do one of the following:
l
Click the Back icon (
>
) at the top of the screen to review the responder configuration.
l
For a
Sorry Server
, click
commit
to add this responder or
cancel
to close the dialog
without adding the responder.
l
For a
Redirect
responder, this screen displays the responder
Redirect URL
and the
Regular Expression
(if supplied).
If you clicked the
test
button on the previous screen, the
Match Components
and
Res-
ulting Redirect
produced by matching the
Test
URL against the
Regular Expression
are
also displayed (any variables appearing in the
Redirect URL
are replaced with strings
from the
Test
URL).
6. Click
Commit
to add the responder or
Cancel
to close the dialog without adding the respon-
der.
Modifying a Responder
1. To modify the configuration of an existing Responder, click on a Responder on the
Responder
branch of the left navigational pane in the left frame.The Responder’s
Configuration
tab
appears.
2. Update the Responder configuration as desired; see
on page 480 for a
description of all Responder parameters.
3. Click
Commit
to save your changes.
Using Regular Expressions in Redirect Responders
In some cases, it may be desirable to examine the URL of an incoming request and re-use parts of
it in the URL returned to the client by a Redirect Responder. This is the purpose of the
Regex
field:
specify a custom regular expression that is used to:
l
parse the URL of an incoming request
l
break it down into separate strings (based on the positions of literal characters in the
expression)
l
assign each string to a named variable
These named variables can then be used in the URL field of the Redirect Responder. When the
Responder replies to a client, it performs string substitution on the URL.
Because the purpose of using regular expressions to perform string substitution in Redirect URLs
is to parse request URLs into strings, constructing an appropriate regular expression requires an
exact knowledge of the format of the request URLs that will typically be coming in to the cluster
IP.
Equalizer supports POSIX-style extended regular expressions.
See the examples that follow below to help you understand how regular expressions are
constructed and interpreted by Responders.
Example 1 - HTTPS Redirect
482
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
Summary of Contents for Equalizer GX Series
Page 18: ......
Page 32: ...Overview 32 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 42: ......
Page 52: ......
Page 64: ......
Page 72: ......
Page 76: ......
Page 228: ......
Page 238: ......
Page 476: ......
Page 492: ......
Page 530: ......
Page 614: ......
Page 626: ......
Page 638: ......
Page 678: ......
Page 732: ...Using SNMP Traps 732 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 754: ......
Page 790: ......
Page 804: ......
Page 842: ......
Page 866: ......