Resolved issues
The following issues have been fixed in FortiProxy 2.0.10. For inquiries about a particular bug, please contact Customer Service & Support.
Bug ID |
Description |
---|---|
784044 | GCP FPX login with username=admin and password=<instance-id> keeps prompting. |
787895 | WAD crash when updating traffic statistic counters. |
796019 | Access issue with Application Control or IPS. |
797270 |
|
799718 |
When |
800262 |
When the |
800268 |
When policy move-next and try-again, not set current policy, which cause use the old policy to match again. |
800499 | SSL/SSH Inspection and Proxy Options are missing on policy page when the action is isolate. |
800873 |
The usage quota fills up quickly, and does not match policy bytes or FortiView user monitor traffic volume. When the usage quota limit is reached, the webfilter logs show the used quota/maximum quota value as zero. |
802333 |
When an HTTPS connection policy match fails, it offers an
implicit deny or allow policy that does not have a |
803217 | Improve policy matching logic for the proxy address category. |
803217 |
Policy matching with multiple category type proxy-address. |
803452 | Fast match
flag is changed from enable to disable after changing settings of
profile-protocol-options . |
805210, 815851 |
NTLM agentless authentication fails due to user-restriction after FSSO service down. |
806224 |
execute ha manage does not work
for unicast HA in a FortiProxy cluster when a trusted host is configured. |
807280 | Proxy certificate error when no policy matched. |
809832 | FPX misses local-in rules for NTP server mode. |
810179 |
Traffic shapers applied to the interface are not working as expected. |
810914 | Classify HTTP transaction log respond types into accurate types. |
811692 | NTLM authentication not working for proxy-chaining. |
813317 |
In transparent mode, |
814398 |
Certificate inspection connection failures when handling TLS 1.3 with early data. |
815458 |
IPv6 issues. |
817750 |
WAD crash when |
820285 |
Masquerade setting added to |