
Match Rules
In other words, the goal is to load balance the highest possible number of requests according to the settings in the
first match rule, which has the effect of reducing to a minimum the amount of match rule processing required for
requests to that cluster.
This is best illustrated by an example. Let’s say you want to construct a set of match rules that achieves these
goals:
l Direct all requests whose URL contains one of two specific directories to specific server pools. Assume
these two directories are.../support and.../engineering.
l Of the two directories above, we expect more requests to contain.../support.
l Load balance requests whose URL
does not
contain a directory across all servers.
l We want to process requests that
do not
contain a directory the fastest, since we expect that 75% of
requests to this cluster will NOT contain a directory in the URL.
The set of match rules that achieves this, their order, and how the match rules are evaluated, is described in the
following figure.
320
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
Kommentare zu diesen Handbüchern