Fortinet 641 FortiWeb 5.0 Patch 6 Administration Guide
Connectivity issues
One of your first tests when configuring a new policy should be to determine whether allowed
traffic is flowing to your web servers.
• Is there a server policy applied to the web server or servers FortiWeb was installed to
protect? If
it is operating in reverse proxy mode, FortiWeb will not allow any traffic to reach a
protected web server unless there is a matching server policy that permits it.
• If your network utilizes secure connections (HTTPS) and there is no traffic flow, is there a
problem with your certificate?
• If you run a test attack from a browser aimed at your web site, does it show up in the attack
log?
To verify, configure FortiWeb to detect the attack, then craft a proof-of-concept that will
trigger the attack sensor. For example, to see whether directory traversal attacks are being
logged and/or blocked, you could use your web browser to go to:
http://www.example.com/login?user=../../../../
Under normal circumstances, you should see a new attack log entry in the Attack Log
Console widget of the system dashboard.
See also
• Checking hardware connections
• Checking port assignments
• Checking routing
• Examining the routing table
• Examining the ARP table
• Debugging the packet processing flow
• Packet capture
• Monitoring traffic load
• Preparing for attacks
Checking hardware connections
If there is no traffic flowing from the FortiWeb appliance, it may be a hardware problem.