https://bugs.openldap.org/show_bug.cgi?id=10060
--- Comment #8 from Ondřej Kuzník ondra@mistotebe.net --- On Wed, May 31, 2023 at 08:05:58PM +0000, openldap-its@openldap.org wrote:
I'm inclined to make this a WONTFIX. Changing a 20+ year old library behavior just seems like a bad idea at this point. (Note that this in particular was also one of the behaviors that was explicitly changed between UMich LDAP and OpenLDAP 1.0. Bugs here go back a long way and any changes will have far-reaching effects.)
That's also an option if we don't want to pull it in 2.7. In that case I could put something like this in the BUGS section of the manpage:
---- 8< ----
BUGS
When there are multiple messages in **result including a result message (common with searches), the return value of ldap_result(, MSG_ALL,) will vary depending on various factors. Some implementations have started relying on this behaviour and as such it is unlikely to be be fixed in the 2.x release series. To get the message type you're looking for, use ldap_first_message() or ldap_parse_result() as needed.
---- 8< ----