hyc@openldap.org wrote:

Full_Name: Howard Chu Version: 2.4 OS:=20 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (110.49.207.42) Submitted by: hyc =20 The result parser is checking for CONTINUE in the wrong place.

Please re-open this ticket. RE24 (tagged as 2.4.41) made things worse.

Is there a chance to get things fixed? I promise to help testing.

First CONTINUE\n works in RE24 better than in 2.4.40 which was the cause = of this ITS.

But handling RESULT is seriously broken, even more than in 2.4.40.

Example:

This is my Python response string:

'RESULT\nmsgid: 1\ncode: 49\ninfo: remote NOK\n\n'

This leads to slapd debug output:

55914b01 str2result (msgid: 1 code: 49 info: remote NOK

) unknown 55914b01 str2result ( ) unknown

Note that the whole string is returned as being unknown.

Also with 2.4.40 my client script receives ' remote NOK' as diagnostic message. With RE24 the diagnostic message is complete garbage.

So I tried many response string variants regarding number of \n and leavi= ng away space after the colon etc. But not really working.

Sometimes slapd hangs, sometimes my client hangs e.g. when sending two subsequent bind requests in one open LDAP connection.