9. Select
Sorry_Example
in the
response
drop-down list on the
Configuration
tab as shown below.
10. Click
Commit
to save the match rule.
Creating a Match Rule to Redirect All Traffic for a Specific URL
Another common cluster configuration requirement is to be able to automatically redirect all
traffic that uses a specific URL. To do this, you need to add a new match rule that:
l
matches any incoming request
l
has a
Redirect
Responder selected
For example, let’s say that we want all traffic to a cluster that uses the URL
to be redirected to
https://www.example.com/special
. The following procedure shows you how to add the appropriate Responder and
Match Rule:
1. Verify that you are logged into the GUI. If not, log in as described in
2. Select the
Load Balance
configuration tab if it is not already selected.
3. Right click on
Responder
on the left navigational pane and select
AddResponder
. The
Add New
Responder
dialog appears.
4. Type
Redirect_Example
into the
Name
field and select
Redirect
.
5.
Type
https://www.example.com/special/
into the
URL
field.
6. Click
Commit
to save the new Responder.
7. Right-click on the name of the cluster for which you want to display the sorry page in the
left frame and select
Add Match Rule
from the menu.
8. Refer to
on page 404 to configure the match rule. Leave the match
rule
expression
set to the default [any()] -- the rule will match all incoming requests. Do
not
select any server pools from the
Server Pool
drop down list. This means that if this match
rule’s expression selects a request, the Responder we select will respond to the selected
request regardless of the status of the server pools in the cluster.
9. Click
Commit
to create the match rule.
10. Select
Redirect_Example
in the
Responder
drop-down list as shown below.
11. Click
commit
to save the match rule.
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
All Rights Reserved.
487
Equalizer Administration Guide
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: ......