extraneous closing tag in LDAP Extended result tree

[asfimport]

mark connolly (Bug 40103):
In a search test, the result tree contains an extraneous closing operation tag.
This prevents the parser from displaying the result as XML.

For example: in the following, the </operation> following </searchresult> should
not exist.

<ldapanswer>
<operation>
<opertype>search</opertype>
<searchfilter>(samaccountname=example)</searchfilter>
<searchbase>ou=bcbsnc users,dc=bcbsnc,dc=com</searchbase>
<scope>2</scope>
<countlimit>0</countlimit>
<timelimit>0</timelimit>
</operation>
<searchresult>
<dn>CN=example,ou=excample,dc=example,dc=com</dn>
<returnedattr>1</returnedattr>
<attribute>
<attributename>displayName</attributename>
<attributevalue>John Smith</attributevalue>
</attribute>
</searchresult>
</operation>
<responsecode>0</responsecode>
<responsemessage>Success</responsemessage>
</ldapanswer>

Severity: minor
OS: Windows XP

Duplicates:

• LDAP Extended Request Search returns invalid XML Document #1799

[asfimport]

Dolf Smits (migrated from Bugzilla):
This is a patch, made against the svn trunk from 3 days ago.
It will solve this problem, has some extra features added and some changes to
the userInterface.
a patch for the manulas is still to be made :-(

Created attachment ldap_ext_patch: Patch for problem, with other enhancements

[asfimport]

Sebb (migrated from Bugzilla):
Thanks very much!

By the way, SVN trunk is rather out of date - 2.2 is built from branch/rel-2-2 -
or is that what you meant?

But I expect the patch can be made to work against the branch anyway.

[asfimport]

Peter Lambrechtsen (migrated from Bugzilla):
*** #1799 has been marked as a duplicate of this bug. ***

[asfimport]

Sebb (migrated from Bugzilla):
The patches did not seem to work properly, even against the revision quoted in
them; however I think it has all now been committed OK.

Please try the nightly build (any after r516970)

[Note that I combined the bind & sbind panels, as sbind needed all the bind
variables anyway]

[asfimport]

Sebb (migrated from Bugzilla):
No problems reported, so assuming fixed