Full_Name: Pierangelo Masarati
Version: HEAD/re24
OS: irrelevant
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (82.63.140.131)
Submitted by: ando
The "dontUseCopy" control requires criticality to be TRUE. While this is the
desirable value, a DUA could use the control with the criticality set to FALSE.
For full conformance with RFC4511, if the control is syntactically well-formed
and criticality is set to FALSE, slapd MUST accept it if recognized, or MUST
ignore it if not recognized, but CANNOT question the fact that the value of
criticality is violating the control's specification.
p.
PS: other controls with similar requirements for the DUA accept any value for
criticality (e.g. RFC4370).
Full_Name: Pierangelo Masarati
Version: HEAD
OS: irrelevant
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (82.63.140.131)
Submitted by: ando
I'm about to add support for what I termed the "What Failed?" LDAP control,
which allows to request detailed information about what extension caused the
failure of a request. The commit includes a preliminary version of what I
intend to submit as an I.D. shortly.
p.