Resolved issues
The following issues have been fixed in FortiProxy 7.0.13. For inquiries about a particular bug, please contact Customer Service & Support.
|
Bug ID |
Description |
|---|---|
|
927635 |
Web proxy in transparent mode cannot match interfaces. |
|
946360 |
Some IPs are not translated to the configured IP pools for HTTPS traffic. |
| 942078 | LDAP admin login in HA cluster secondary not successful due to invalid DNS request. |
| 941755 | FPX-400G platform configuration has the wrong maximum number of wad workers. |
| 941045 | Local rating picks the wrong category when URL path false matches to a longer local rating URL. |
| 846986 | IPsec monitor widget resets incoming and outgoing data counter. |
| 916276 | FortiProxy memory leak consuming a lot of memory. |
| 945012 | Admin name containing spaces breaks trusthosts. |
| 945257 | GUI shows PAC policy while the user's admin profile is configured with System Read/Write. |
| 946369 | FortiProxy HA cluster status is out of sync. |
| 910115 | NTLM authentication times out for no reason. |
| 903680, 950931 | Antiphishing scan stops after checking the first potential username. |
| 940162 | FPX_VMWARE should be categorized as high end model. |
| 940447 | SSLVPN frds service can be abused by authenticated users to cause memory leak. |
| 948142 | Memory utilization increases after upgrade. |
| 951054 | GUI user group information is inconsistent with CLI configuration. |
| 942346 | DNS proxy updates captive portal FQDN IP set with 0 IPs, causing IP tables to drop auth packets. |
| 946730 | WAD returns true when there is an error in decode base64. |
| 949538 | When "gui-ipv6" is disabled under global, the IPv4 destination object is miss in the authentication rule in GUI. |
| 783549 | WAD crash with signal 11. |
| 902613, 929182 | WAD crash during stress testing. |
| 912116 | Some websites do not work using deep inspection and proxy inspection. |
| 921247 | WAD worker consumes high memory and CPU. |
| 949040 | WAD process causes memory leak for session-based authentication rules. |
| 918191, 947814 | WAD crash caused by a corruption or an issue that causes authentication loop. |
| 940378 | "Entry not found" error when configuring wildcard FQDN address of explicit FTP in GUI. |
| 946567 | "diagnose sys tcpsock" does not show anything. |
| 951131 | Unused IP sets are not always cleaned up. |
| 897347 | WAD user-info memory leak. |
| 924644 | Explicit proxy with forwarding server and URL list does not work. |
|
955857 |
WAD crash at HTTP HEAD request or unknown Content-Type with webfilter content-header action = block. |
|
951070 |
WAD local AV scan blocks traffic when DLP profile is in place but no AV profile is set. |
|
938821 |
HTTP explicit fails when multiple web proxy entries for the interface and SOCKS is enabled on the same port as HTTP. |
|
947926 |
WAD crashes @wad_crash_table_load repeatedly. |
|
952694 |
FortiProxy-4000E scanunit daemon crashes continuosly at load_SearchFile. |