Match Rules
7. Click on Commit.
The images rule we created selects all the requests for image files; now we need a rule to determine which
servers will receive all the other requests. The Default rule is not sufficient, and in fact we don’t want it to be
reached, since it could send a request for content to one of the image servers. So, we’ll create another rule with the
same match expression as the Default [any()], but a restricted list of servers. This effectively
replaces
the Default
match rule with one of our own.
8. In the left frame, right-click the name of the cluster and select Add Match Rule. The Add Match Rule
screen appears:
a. Type “content” into the match name text box and use the Next Match Rule drop-down list to
specify the match rule order for this match rule on the selected cluster. Click on Commit.
b. On the Configuration screen (tab) use the drop-down list to select the server pool in which
all other content is to be sent.
c. Select Commit.
The match rule is created, added to the object tree, and its Configuration Screen (tab) is opened:
9. Check the Persist checkbox. (Remember that in our example we’re enabling Persist for the content
servers, so that persistent sessions can be maintained by the applications that run on these servers.)
10. Select the Commit button to save your changes to the Content rule.
Using the Match Rule Expression Editor
The Match Rule Expression Editor shown below is a feature of the GUI that allows the user an easy method of
building Match Expressions. As described in "Match Rule Expressions and Bodies" on page 321, Match
Expressions are made up of match functions, most of which are protocol-specific, joined by logical operators,
optionally preceded by the negation operator, with sets of beginning and end parentheses for grouping where
Match Bodies required. The Expression editor allows the user to drag and drop functions and operators to build the
desired expressions.
344
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
Comentários a estes Manuais