Resolved Issues
- Last Updated: November 8, 2023
- LoadMaster
- LoadMaster LTSF
- Documentation
| LM-114 | GEO: When GEO is running in Cloud High Availability (HA) Mode, DNS remains running on the standby unit as well as the active unit. This issue has been fixed. |
| LM-113 | Single Sign On - LDAP:
Fixed issues associated with LDAP SSO no longer working after an
upgrade to LMOS 7.2.53. The issues appeared in conjunction with log
messages like the following: ssomgr: ... Couldn't bind: [LDAP-AD] [ip-addresses-omitted]: 32, No such objectssomgr: do_sso_ldap_check: Could not get ldap_result for (credentials-omitted): 32 [No such object] |
| LM-108 | Caching: Fixed an issue that caused expired cache entries to remain in the cache after the associated Virtual Service is stopped and restarted. |
| LM-86 | HTTP/2 and Chrome: Fixed issues that could cause random client reconnect issues when accessing a website using the Chrome browser. |
| LM-85 | WAF / ESP: Fixed an issue where modifying the WAF or ESP configuration of a Virtual Service can cause the LoadMaster to reboot. |
| LM-83 | Layer 7: Fixed an internal issue that could cause memory exhaustion under very heavy load. |