Resolved issues
This section highlights the major known issues discovered in FortiADC 5.3.2 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.
Known issues
Bug ID | Description |
---|---|
0579500 | Parameter validation doesn't work in some circumstances |
0575698 | Deleting L7-Turbo-HTTP VS with empty real-server-pool and persistence could lead to a crash. |
0575231 | DDOS function performance improvement |
0567820 | 0 in "max-access-count" is improved to mean unlimited. |
0573226 | Support WAF OWASP wizard feature |
0577637 | Improvement of the CSRP CPS performance |
0567939 | Improvement of the throughput performance for L7-VS SSL traffic |
0568014 | Optimizing the country matching algorithm when the GEO library is G20. |
0572204 | HSM work for non-vdom users will cause a crash in some circumstances |
0534085 | The OCSP cache item should be cleared while changing OCSP memory size. |
0568196 | FortiADC - CVE-2019-11478 Excess Resource Usage (all Linux versions) and SACK Slowness (Linux < 4.15) |
0568192 | FortiADC - SACK Panic attack: CVE-2019-11477 |
0574844 | Added new feature to make GUI show the interface speed |
0544549 | GUI improvement to make WAF signature table entries sortable |
0574266 | The event log does not show correctly in specific circumstances |
0574789 | A configuration which has a key-file with no pass phrass cannot be restored properly using the backup file. |
0575586 | Choosing dual certificates by servername fails |
0565447 | Supports instance types M4, M5 and C5 on AWS platform. |
0574030 | Too many client authentication request tries are shown in clone traffic. |
0573478 | The HA-status on the webpage is not being updated immediately |