There was a missing break in the WAN optimization explicit proxy component.

After activating FortiCloud, the user could not enable FortiSandbox Cloud.

The IP pool configuration in an explicit policy is ignored on outbound traffic.

LACP fails when an HA cluster is configured.

There are too many TIME_WAIT sessions after the admin user logs in to the GUI.

The set ssl-ssh-profile command works in the CLI but not in the GUI.

Users cannot download the PAC file when the pac-file-server-port is set to a different port than the proxy port.

The FortiProxy VM in Azure does not restart properly after the execute reboot command.

After creating an HA cluster in Config-Sync mode, the FortiProxy units cannot be accessed because of a memory leak.

The explicit proxy settings differ in the CLI and GUI.

From the System > Replacement Messages page, some of the pages mention FortiGate instead of FortiProxy.

Trying to preload cache content results in error 255.

After adding the Quarantine Monitor widget to the dashboard, the new widget does not load data.

When a policy has Internet service addresses in the Destination field, the Destination field is blank in the GUI.

The Safe Search option is available in the CLI but not in the GUI.

You cannot import a certificate without adding a password.

When Isolate is selection for the action in a new policy, some options are missing in the GUI.

The DLP log cannot be viewed in the GUI.

The HTTP Proxy-Authorization/Authorization header needs to be removed to prevent user credential leaking.

After FortiProxy is upgraded from 2.0.6 to 7.0.1, the UUIDs do not match in the proxy address groups in an HA cluster.

The WCCP cache engine cannot be enabled or disabled in the GUI.

DNS protection not working in the transparent proxy policy.

The WAD crashes multiple times after the user upgrades from FortiProxy 2.0.6 to 7.0.1.

The diagnose hardware deviceinfo nic command does not work in FortiProxy 7.0.1.

The set http-view command does not appear under config system global.

FortiManager 7.0.3 does not support FortiProxy 7.0.1.

After upgrading from FortiProxy 2.0 to 7.0, the fields of the antivirus profile are unset.

After using the set ha-mgmt-status disable command, connecting with Telnet does not work.

Zero-trust network access traffic needs to keep the setting of the source-affinity flag.

Upgrading the firmware of a FortiProxy unit that is a member of an HA Config-Sync cluster causes a wa_cs crash.

After upgrading to build 0051, CRWL keeps crashing.

When the destination is ISDB for a transparent policy, traffic is not forwarded.

When ICAP is enabled for web proxy and cURL is used to send a file, the contents of the Submitted By field are corrupted.

The WAD crashes if the authentication rule configuration is updated while WAD is synchronizing.

The set host-regex command is not working correctly.

When the ICAP local server is configured, the ICAP server crashes.

When traffic is sent to a transparent proxy policy, the FortiProxy unit crashes.

When a proxy address is used as the destination in a policy, unrelated traffic matches the policy.

URL filter is not blocking a specific page while allowing access to other pages for that domain.

The following commands do not work:

• diagnose ipv6 neighbor-cache list

• diagnose ipv6 route list

• diagnose ipv6 address list

When antivirus caching and inspect-all are enabled, the cached infection scanning results are not used in the FTP download.

After deleting a new system administrator, the CLI responds with an error message, “Add table index error: type=4.”

Preloading cache content fails with error 4 and causes a WAD crash.

The set ztna-ems-tag command is not working.

The infection cache needs to skip content when the size is 0.

After upgrading the Azure FortiProxy VM from build 0050 to build 0054, the VM does not start.

After upgrading the GCP FortiProxy VM from build 0047 to build 0054, the VM keeps restarting.

The WAD keeps crashing when the service for the IPv4 API gateway is set to the web portal without a predefined bookmark.

There is a MAC address conflict after enabling the LAG interface in FortiProxy 7.0.1.

Upgrading the firmware in an HA Config-Sync cluster fails.

The forward traffic logs do not display the FSSO user names.

The config web-proxy explicit command has been changed to config web-proxy explicit-proxy.

After upgrading from FortiProxy 2.0.7 to 7.0.0, multiple errors 160 are logged.

There was an unintentional integer overflow in the WAN optimization explicit proxy component.

A dereference-after-null-pointer problem was found in the WAN optimization explicit proxy component.

The wrong sizeof argument was used in the WAN optimization explicit proxy component.

After FortiProxy is upgraded to build 0057, the WAD keeps crashing.

The FortiProxy 400E reports that “Maximum WAD worker count 4 is not equal to current cpu number.” when it starts.

When the ICAP server returns an HTTP message other than 200, the client gets an empty reply instead of the actual HTTP message.

The HTTP and HTTPS daemon keeps crashing.

When the FortiProxy unit is in transparent mode, NTLM authentication does not work.

A WAD memory leak occurs when using ICAP.

After the web-proxy entry is deleted, the WAD must be manually restarted for the change to be learned.

When fast-match is disabled, the HTTPS request fails to match the source proxy address in the policy.

After the policy type is changed to explicit, the address in the firewall policy cannot be edited in the GUI.

When using the Active-Passive mode in an HA cluster, the primary unit crashes during synchronization.

The WAD should use the port in the TCP header to match the service field.

When the FortiProxy units are in HA Config-Sync cluster, the secondary unit displays ha req read header error:1 type:59 in the console.

When proxy inspection is enabled with at least one flow feature (such as IPS or Application Control), all connections to all websites fail and an ERR_EMPTY_RESPONSE is reported.