l load balance all other requests across all of the servers
Match Rules are constructed using match functions that make decisions based on the following:
l HTTP protocol version; for HTTPS connections, the SSL protocol level the client uses to connect.
l Client IP address
l Request method (GET, POST, etc.)
l All elements of the request URI (host name, path, filename, query, etc.)
l Pattern matches against request headers
Match functions can be combined using logical constructs (AND, OR, NOT, etc.) to create extremely flexible
cluster configurations. See "Using Match Rules" on page 318 for an overview of Match Rules, a complete list of
match functions, and usage examples.
Server Selection Process Flow
The figure below shows the server selection process. As describe above, this process depends on whether
persistence is in use. Once a server is selected, Equalizer verifies that it isn’t too busy (based on max_
connections) and that it has been probed up. Then Equalizer tries to connect to it.
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
All Rights Reserved.
35
Equalizer Administration Guide
Comentarios a estos manuales