FortiWeb allows you to configure policy routes that direct traffic away from a static route. This mechanism can be useful for the following tasks:

Policy routes direct traffic to a specific network interface and gateway based on the packet’s source and destination IP address. In addition, you can also specify the interface on which FortiWeb receives packets it applies this routing policy to.

In most cases, you use policy routes when FortiWeb is operating in reverse proxy mode. In this mode, FortiWeb opens its own HTTP connection to the back-end server (a server pool member) and does not transmit the client’s request to the pool member. Because the pool member’s reply contains no incoming interface information that FortiWeb can use to route the reply, you do not specify an incoming interface value to match. Instead, the policy route specifies a source address (for example, the virtual server’s IP address), outgoing interface, and gateway only.

In other operating modes (true transparent inspection, transparent inspection, and offline protection), specifying an incoming interface in the policy route configures FortiWeb to act as a router.