Issues Resolved
- Last Updated: November 8, 2023
- LoadMaster
- LoadMaster LTSF
- Documentation
| PD-18022 | IPv6: If packet filtering is enabled, returning IPv6 traffic destined for a Real Server acting as a client is ignored by LoadMaster. This issue has been fixed. |
| PD-17940 | Wildcard VS: After upgrade to 7.2.53, Loadmaster may reboot if a Wildcard Virtual Service exists and connections are not completed by the client. This bug has been fixed. |
| PD-17921 | Body Response Content Rules: Fixed an issue where a body response rule applied to an empty file causes a significant response delay. |
| PD-17878 | Bandwidth Limiting Statistics: Fixed an issue that caused incorrect client bandwidth limiting statistics to be displayed. |
| PD-17721 | SSL Certificate Login: Fixed issues associated with rejecting certificates with an unknown user error when multiple "Other names" are specified in the certificate. |
| PD-17717 | WAF: Addressed issues where a specific custom WAF rule could not be added because of internal dependencies within the standard rule set. |
| PD-17714 | OIDC: In previous releases, the minimum allowed value for the Application Secret ID length was 32, which caused issues on some providers. With this release, the minimum value is 1. |
| PD-17694 | User Interface: Fixed an issue with rendering the Network Telemetry interface table in some browsers. |
| PD-17693 | ESP Logging: In previous releases, Layer 7 User Agent logs were appearing in the messages log file when accessing a Virtual Service using Single Sign On even when Layer 7 Debug Logs were not enabled. This issue has been fixed. |
| PD-17636 | UDP Virtual Service: Fixed an issue that caused the system to panic when a UDP port 443 Virtual Service was created. |
| PD-17616 | CSR Generation: In previous releases, the T61STRING string type was used for the Common Name field of a Certificate Signing Request (CSR) created by LoadMaster. With this release, LoadMaster uses the UTF8STRING string type for the Common Name. |
| PD-17612 | Licensing: Fixed an issue with licensed bandwidth limits where Virtual Services with SubVSs would be prematurely limited. |
| PD-17504 | SSL: Fixed an issue that caused SSL handshakes to fail between LoadMaster and a Real Server with certain types of EC certificates. |
| PD-17308 | Body Response Content Rules: If a user adds a body response rule to a Nested/Cascaded Virtual Service the LoadMaster removes all "Set-Cookie" headers. This bug has been fixed. |
| PD-17207 | API: Using the killsession API to end an SSO session results in an overflow error. This issue has been fixed. |
| PD-16707 | SSO: Steering Groups: Fixed an issue where a user would close the browser and get an error logging into the application again using a steering group. |
| PD-16495 | GEO: Fixed an issue where adding an IP address of 0.0.0.0 to an FQDN caused issues. Now, 0.0.0.0 is blocked from being added to an FQDN. |
| PD-16113 | GEO: LoadMaster adds the Global TTL to TXT records when local settings are enabled on the FQDN. This issue has been fixed; now, the Local TTL is added when local settings are enabled. |
| PD-15396 | GEO: Fixed an issue that caused LM to send a spurious "KEMP GEO" TXT record in DNS responses, if the TXT record field is empty and the queried FQDN is not a sub-domain of the ZoneName. |