Issue 4591 - back-meta does not propagate response controls
Summary: back-meta does not propagate response controls
Status: UNCONFIRMED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: backends (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-14 12:06 UTC by ando@openldap.org
Modified: 2020-03-18 20:24 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description ando@openldap.org 2006-06-14 12:06:58 UTC
Full_Name: Pierangelo Masarati
Version: HEAD
OS: irrelevant
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (81.72.89.40)
Submitted by: ando


In most cases, all response payload (matched, referrals) is ignored when calling
ldap_parse_result(); only in searches matched and referrals are handled.

p.

Comment 1 ando@openldap.org 2006-06-14 12:07:20 UTC
changed notes
moved from Incoming to Software Bugs
Comment 2 ando@openldap.org 2006-06-17 10:37:26 UTC
changed notes
Comment 3 ando@openldap.org 2007-01-15 11:45:43 UTC
ando@sys-net.it wrote:

> In most cases, all response payload (matched, referrals) is ignored when calling
> ldap_parse_result(); only in searches matched and referrals are handled.

For most operations this should now be fixed, since response passes thru 
   meta_back_op_result(), which takes care of controls.  However, in 
case of searches, handling this issue may be problematic, as different 
targets may return different, possibly overlapping or incompatible 
controls in response, so ignoring them might be safe.  A minimal, 
forgiving approach could be to record response controls, and, in case 
only one target returned any, use them; otherwise, either ignore them or 
complain somehow.

p.

Comment 4 OpenLDAP project 2014-08-01 21:04:13 UTC
partially addressed by fix to ITS#4594