Resolved issues
The following issues have been resolved in FortiADC 6.0.2 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.
Bug ID | Description |
---|---|
0685661 | SQL Injection is not recognized by WAF signatures. |
0684903 | Web-Filter Category lookup fails intermittently. |
0682666 | Admin user with Read-only access can still change network interface settings. |
0682395 | 408 timeout issue. |
0679167 | FortiADC unable to save configuration due to oldschool ssh library. |
0678787 | LDAP config doesn't work, which is caused by empty passwd. |
0677217 | Block view goes blank and FortiADC disappears off map. |
0676693 | HA Active-Passive: any change results in Not in Sync, which is caused by special characters in cert. |
0676126 | Memory starts to increase after a while (Restapi). |
0675022 |
FortiADC makes unsolicited connection to FortiToken Cloud |
0674702 | Virtual Server Stops Processing Traffic. |
0674244 | FortiADC doesn't close the TCP connection with the client when hardware SSL is turned on in the Virtual Server. |
0673592 | GLB stops completely due to invalid zone txt record. |
0673408 | High Memory Usage caused by infod. |
0670818 | HA manual synchronization results in timeout as per CLI output. |
0670544 | L2 exception list member to 1K. |
0670346 | FortiADC doesn't generate RESET right away when the mapped real server is declared by HC as dead in L4 mode. |
0670196 |
High CPU/memory usage caused by infod. |
0670149 | One Virtual Server Stops working, which is caused by scripting. |
0663021 | FortiADC ignores the rt-cache-reverse-exception configuration when it looks up for the MAC address. |