Fortinet 265 FortiWeb 5.0 Patch 6 Administration Guide
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:
• 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 would configure HTTP content routing so FortiWeb routes HTTP requests to
http://www.example.com/school to the appropriate back-end web server, 10.0.0.12. Similarly,
requests for the URL /games would go to 10.0.0.11, and requests for the URL /work would go
to 10.0.0.13.
See also
•Routing based upon URL or “Host:” name
•Defining your web server by its IP address
•Grouping your web servers into server farms
•Configuring server up/down checks
Example: Routing according to the HTTP “Host:” field
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, Example Company’s web site has a
few domain names:
• http://www.example.com
• http://www.example.cn
• http://www.example.de
• http://www.example.co.jp
Public DNS resolve all of these domain names to one IP address: the virtual server on FortiWeb.
At the data center, behind the FortiWeb, some region-specific web sites are each hosted on
separate physical web servers. Others have lighter traffic and are maintained by the same
person, and therefore are hosted on a shared server. Each back-end web server has a DNS