Defining your web servers & load balancers : Defining your web servers : Creating a server pool : Example: Routing according to URL/path
 
Example: Routing according to URL/path
Your FortiWeb appliance might have one virtual server (the front end) protecting three physical web servers (the back end).
From the perspective of clients connecting to the front end, there is one domain name: www.example.com. At this host name, there are three top-level URLs:
/games — Game application
/school — School application
/work — Work application
In a client’s web browser, therefore, they might go to the location:
http://www.example.com/games
Behind the FortiWeb, however, each of those 3 web applications actually resides on separate back-end web servers with different IP addresses, and each has its own server pool:
10.0.0.11/games — Game application
10.0.0.12/school — School application
10.0.0.13/work — Work application
In this case, you configure HTTP content routing so FortiWeb routes HTTP requests to http://www.example.com/school to the server pool that contains 10.0.0.12. Similarly, requests for the URL /games go to a pool that contains 10.0.0.11, and requests for the URL /work go to a pool that contains 10.0.0.13.
See also
Routing based on HTTP header content, source IP, or cookie
Creating a server pool
Configuring server up/down checks