Load balancing : Load balancing among local servers : Distributing new sessions among your servers : Routing based on the application layer
Routing based on the application layer
You can route packets to your back-end servers based upon the application layer header rather than the TCP/IP layers. For example, you could route computationally-heavy web pages always to the same server.
Alternatively, for traffic that your FortiADC is load balancing, you can also control the direction which FortiADC forwards packets by using:
static routes (“Adding a gateway”) and/or
policy routes (see “Policy routes”)
For information on how FortiADC chooses between the multiple packet forwarding methods that may apply, see “Sequence of packet routing evaluation”.
Before you can configure content routing, you must first define your pool of servers so that you can specify packet destinations for each content route. See (“Defining your pool of back-end servers”).
To configure application content-based routes, go to Server Load Balancer > Content Rules > Content Routing Rule.
If you need to create a default route, create a condition that does not have any expression, then place it last in the condition table. This will match all requests that did not match any previous criteria.