The following issues have been resolved in FortiADC 7.0.0 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.
|0774662||WAF signature details page displaying overlapping text.|
CPU spikes occurring in both of the paired FortiADC units due to the DNSPod multi-thread daemon accessing null schedule data when the DNS request is very high.
WAF unable to detect the expected attack when the requests contain Non-US-ASCII characters.
|0770832||Debug producing junk output.|
Unable to register in FortiCare from AWS with FortiADC PAYG instance.
CLI returning wrong system status information despite GUI displaying correct license information for the IPS related service.
|0769717||GUI does not allow the comment field to be empty for the local certificate configuration.|
|0769573||Telnet and SNMP are enabled by default on port1.|
|0768416||Unable to unset mail server address.|
|0768119||HA device repeatedly asking for license.|
|0766854||Cookie-security WAF rule causing VS-persistence to fail.|
|0766441||Unable to configure the WAF exception rules via GUI.|
|0765729||Spelling error: L3 Trasnparent Proxy → L3 Transparent Proxy.|
|0761550||FortiADC may reboot multiple times during upgrade when not using HA sync upgrade in HA environment.|
|0756750||Health check via GUI is not working properly for VDOM.|
|0754313||WAF Parameter Validation does not work when forming an action with no path.|
|0753788||There is no length restriction for NAT Pool name in GUI.|
|0751900||Spelling error: vitrual → virtual.|
|0751761||FortiADC administrator users are limited to control no more than 8 VDOMs per user.|