On Tue, 16 Dec 2003, Chris Ridd did scribble:
> I can't really recall the details of the original problem, except I think
> the ASN.1 got screwed up somehow so we were sending rubbish (legal BER, but
> the wrong ASN.1) to the server. I can't remember when it was broken or what
> version fixed it :
On Tue, 16 Dec 2003, Chris Ridd did scribble:
> I can't really recall the details of the original problem, except I think
> the ASN.1 got screwed up somehow so we were sending rubbish (legal BER, but
> the wrong ASN.1) to the server. I can't remember when it was broken or what
> version fixed it :
On 31/12/03 8:26 pm, D.Kreft <[EMAIL PROTECTED]> wrote:
> On Tue, 16 Dec 2003, Chris Ridd did scribble:
>
>> I can't really recall the details of the original problem, except I think
>> the ASN.1 got screwed up somehow so we were sending rubbish (legal BER, but
>> the wrong ASN.1) to the server.
On 31/12/03 9:45 pm, D.Kreft <[EMAIL PROTECTED]> wrote:
> On Wed, 31 Dec 2003, Chris Ridd did scribble:
>
>> There's at least one way where these methods return a non-object. Mostly
>> they call _error() to set an error code in a message object, but this isn't
>> always true - if $ldap->socket fai
On Wed, 31 Dec 2003, Chris Ridd did scribble:
> There's at least one way where these methods return a non-object. Mostly
> they call _error() to set an error code in a message object, but this isn't
> always true - if $ldap->socket fails the integer LDAP_SERVER_DOWN is
> returned (NB this is 81, s
