upstream/openldap
1
0
Fork 0
mirror of https://git.openldap.org/openldap/openldap.git synced 2025-12-25 09:09:54 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

ITS#8255 Clarify "sockresps result" behaviour

Browse source
This commit is contained in:
Ondřej Kuzník 2022-01-31 10:48:33 +00:00 committed by Quanah Gibson-Mount
parent 4996d42277
commit 73e882c87f
1 changed files with 24 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

29
doc/man/man5/slapd-sock.5
View file

@ -193,11 +193,19 @@ CONTINUE response if request processing should continue normally, or
a regular RESULT response if the external program wishes to bypass the
underlying database.
If the overlay is configured to send response messages to the external
program, they will appear as an extended RESULT message or as an
ENTRY message, defined below. The RESULT message is similar to
the one above, but also includes the msgid and any configured
extensions:
If
.B sockresps
includes
.BR result
or
.BR search ,
the overlay will also send any response messages to the external program (also
see KNOWN LIMITATIONS). These will appear as an extended RESULT message or an
ENTRY message respectively, both are defined below and the program is not
expected to respond to these.
The extended RESULT message is similar to the one above, but also includes the
msgid and any configured extensions:
.RS
.nf
RESULT
@ -225,6 +233,17 @@ The
.B sock
backend does not process extended operation results from an external program.
If
.B sockresps
is configured,
.B sock
overlay does not consider
.B sockops
nor
.B sockdnpat
to decide which responses are passed onto the external program, instead, all
responses are currently passed on.
.SH ACCESS CONTROL
The
.B sock