Description | This article describes how to do an explicit proxy policy lookup from the CLI with the FortiProxy. |
Scope | FortiProxy. |
Solution |
On a FortiProxy, it is possible to run an explicit proxy policy lookup using the following command:
diagnose wad exp-fw-policy-test <SRC> <WEBPROXY> <REQ> <AUTH-TYPE> [<USERNAME/GROUP>] [<SERVER>]
diagnose wad exp-fw-policy-test Usage:
The output will show the matching policy ID. If the traffic is accepted or blocked, source and destination addresses are configured in the policy and matching user/group.
diagnose wad exp-fw-policy-test 10.1.1.1 web-proxy "ipport=1.1.1.1:443" user user1 local
In the following example, as user1 belongs to the group usr-grp, traffic will match policy 5 and will be denied:
diagnose wad exp-fw-policy-test 10.1.1.1 web-proxy "ipport=1.2.3.4:443" user user1 local
diagnose wad exp-fw-policy-test 10.1.1.1 web-proxy "uri=https://google.com" none
If no explicit proxy policy is matched, the implicit deny will match and the output will be as follow:
diagnose wad exp-fw-policy-test 1.1.1.1 web-proxy "uri=https://facebook.com" none
Note: This command will not work on a FortiGate, even if the FortiGate can have explicit proxy policies. It is only valid for FortiProxy. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.