Fortinet black logo

Resolved issues

Resolved issues

This section highlights the major resolved issues discovered in FortiADC 5.3.4 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.

Resolved issues
Bug ID Description
0596982 Added back lbdns debug method
0596233 Did some optimization for showing the server pool status when content-routing is used
0596151 The SSL server-hello fails sometimes in some cipher combinations when working with Windows Chrome browser
0596200 Authentication Relay with “Domain Prefix Support” failed for Kerberos user principle test
0593358 Source Address (in CLI, client-address) cannot be enabled in load-balance profile
0593580 GUI can not be accessed in some circumstances
0595777 Corrected the error warning message: sftp to ftp
0571895 Corrected the incorrect port information while upgrading waf-signature
0558607 The HA config sync may fail in particular situations
0566201 Added XSS prevention in the WAF page
0536745 Vertical axis is incorrect on fortiview chart
0593281 Added memory leak prevention for vdom in some potential situations
0527984 Long name of vdom exceed frame
0588765 "VM Registration" of FortiADC selected as slave becomes "Pending" from "Valid" after establishing HA
0590421 The licd process may consume high memory in some cicumstances
0516063 Optimized the SSL/TLS debug message.
0564542 No error message to block creating wad profiles that exceed maximum in different vdoms.
0579794 SIP type VS may crash in some high stress cicumstances
0590120 WAF URL exception fails in some circumstances
0599700 Default value of Max Receive Window which displays under "HTTP2 Profile" tub is different from entry field value
0595611 Improve the behavior or recover time between regular RS and backup RS when the method is least-connection
0598653 Add the long length support for TXT record
0573877 GLB CNAME record name should not the same as other records
0597406 Fixed the crash which happens in certain circumstances
0592830 Made the improvement to avoid the potential L4-VS crash in some particular conditions
0597684 DoS protection may not work in certain condition on devices that have a large amount of memory

Resolved issues

This section highlights the major resolved issues discovered in FortiADC 5.3.4 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.

Resolved issues
Bug ID Description
0596982 Added back lbdns debug method
0596233 Did some optimization for showing the server pool status when content-routing is used
0596151 The SSL server-hello fails sometimes in some cipher combinations when working with Windows Chrome browser
0596200 Authentication Relay with “Domain Prefix Support” failed for Kerberos user principle test
0593358 Source Address (in CLI, client-address) cannot be enabled in load-balance profile
0593580 GUI can not be accessed in some circumstances
0595777 Corrected the error warning message: sftp to ftp
0571895 Corrected the incorrect port information while upgrading waf-signature
0558607 The HA config sync may fail in particular situations
0566201 Added XSS prevention in the WAF page
0536745 Vertical axis is incorrect on fortiview chart
0593281 Added memory leak prevention for vdom in some potential situations
0527984 Long name of vdom exceed frame
0588765 "VM Registration" of FortiADC selected as slave becomes "Pending" from "Valid" after establishing HA
0590421 The licd process may consume high memory in some cicumstances
0516063 Optimized the SSL/TLS debug message.
0564542 No error message to block creating wad profiles that exceed maximum in different vdoms.
0579794 SIP type VS may crash in some high stress cicumstances
0590120 WAF URL exception fails in some circumstances
0599700 Default value of Max Receive Window which displays under "HTTP2 Profile" tub is different from entry field value
0595611 Improve the behavior or recover time between regular RS and backup RS when the method is least-connection
0598653 Add the long length support for TXT record
0573877 GLB CNAME record name should not the same as other records
0597406 Fixed the crash which happens in certain circumstances
0592830 Made the improvement to avoid the potential L4-VS crash in some particular conditions
0597684 DoS protection may not work in certain condition on devices that have a large amount of memory