Gerardo Herzig writes: > Hi dudes. I have a python/cgi app who interacts with an ldap > server. The thing is, sometimes ldap server allows the cgi to make > some changes, some times it does not. Same app, same user, same > change...
You are not waiting for results from previous operations before sending the next. With some exceptions, the LDAP server can process incoming operations in any order. Unbind (and for that matter Bind) may discard outstanding operations. Which is what happens when the server is busy and defers the Bind, and then sees your Unbind. The LDAP standard (RFC 4511) does in any case require that you wait for the result from Bind before sending other operations. But you are not reqired to wait for other operation results before sending the next, except you must wait before and after StartTLS. -- Hallvard
