11106 - Problems when updating single attribute with multiple values

Status: VERIFIED DUPLICATE of bug 4369

(Directory :: PerLDAP, defect, P3)

Description

[Leif Hedstrom]

Hi Kevin,

I'm opening this new bug, I suspect it might be related to the other fixes
you've done, but perhaps you can check it out?


---------------


From: Basil <[e-mail]>

Greetings,

        I'm using perLDAP v1.22 and get Internal server error
        ever other time when I do an LDAP update within my CGI
        script (I'm using CGI.pm).  I have parsed through the
        code line by line and have narrowed it down to the following:

        $conn->update($entry);

        Here's the script (i left out all the conn/entry variables):

        $conn = new Mozilla::LDAP::Conn();
        $entry = $conn->search();
        # i get one entry from my search filter above.

        $entry->{attr} = ["$CGI::attr1","$CGI::attr2"];
        $conn->update($entry);
        $conn->close;

        The $conn->update($entry) works *ever other time*. It works
        every time if I don't update multiple values for the single
        attribute at once.  It also breaks if one of the values is
        null.

        But wait, there's more..  The update actually works in all
        cases but it freaks out Apache or Perl and I get "server error".
        $conn->printError even prints "Success"..  I don't know enough
        about perl internals to know what happens when the update method
        gets called.

        What's really wierd is that I can't get any error info out of
        perl and apache (1.3.6) only says "premature header from script"
        even when I *forced* print headers at key parts of the code as
        I was trying to find this perceived bug.  The premature header
        error made me think there was something wrong with my code or
        Apache (mod_perl residue), but I spent all day today isolating
        the culprit and I'm not even using mod_perl. ;)

        My guess is that perldap doesn't like or handle well, the
        updating of a single attribute name with multiple values.

        -keith

Comment 1

[Kevin McCarthy]

This is very likely to be caused by the bug in bug 10431.  I will ask the
reporter to try out the patch file and see if that fixes the problem.

Comment 2

[Leif Hedstrom]

*** This bug has been marked as a duplicate of 4369 ***

Comment 3

[Sebastian Späth]

cleaning up: VERIFY duplicate