Known issues
This section lists known issues in version FortiADC 7.2.1, but may not be a complete list. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.
|
Bug ID |
Description |
|---|---|
| 0900830 | After the automation rule is triggered for a long time, the memory usage may not be recycled. This may happen when a vast number of logs are triggered by automation rules and the action takes a long time to be completed. |
|
0898316 |
Apply-to-All-CORS-Traffic should only take effect with HTTP requests with header "Origin". |
| 0885240/0884177 | Due to FortiGate Cloud portal upgrade, statistics from FortiADC boxes can not be shown on their Sandbox portal. |
|
0881992 |
Request for L7 DNS SLB to support forwarding of all DNS responses. |
|
0875797 |
For the server-load-balance L7 virtual-server type explicit_http, the resolve host responds with incorrect IP address at certain condition. |
|
0859565 |
After executing factory reset, the console shows the message indicating that the "bind failed" due to the address already being in use. |
|
0838441 |
The same IP address can be configured on two different interfaces, with one being the static IP and the other from PPPoE. |
|
0835874 |
Should be able to control minimal-responses to enhance named performance. |