Commit 53baebac authored by Quanah Gibson-Mount's avatar Quanah Gibson-Mount
Browse files

ITS#5718

parent 3dececd4
......@@ -53,11 +53,12 @@ OpenLDAP 2.4.12 Engineering
Added BDB 4.7 support (ITS#5523)
Added slapo-collect overlay with enhancements(ITS#5659)
Documentation
Added slapo-collect(5) man page (ITS#5706)
Added slapd-ldap(5), slapd-meta(5) noundeffilter (ITS#5614)
Fixed slapd-ldap(5), slapd-meta(5), slapo-pcache(5) schema requirements (ITS#5680)
Added slapo-collect(5) man page (ITS#5706)
Added slapo-pcache(5) proxycheckcacheability option (ITS#5680)
Added slapo-retcode(5) retcode.conf location (ITS#5633)
admin24 dontusecopy control update (ITS#5718)
admin24 guide updates (ITS#5616)
admin24 octetString fix (ITS#5670)
......
......@@ -322,6 +322,20 @@ side, the actual error is returned to the client.
> chain-return-error TRUE
H3: Read-Back of Chained Modifications
Occasionally, applications want to read back the data that they just wrote.
If a modification requested to a shadow server was silently chained to its
producer, an immediate read could result in receiving data not yet sync'ed.
In those cases, clients should use the {{B:dontusecopy}} control to ensure
they are directed to the authoritative source for that piece of data.
This control usually causes a referral to the actual source of the data
to be returned. However, when the {{slapo-chain(5)}} overlay is used,
it intercepts the referral being returned in response to the
{{B:dontusecopy}} control, and tries to fetch the requested data.
H3: Further Information
{{:slapo-chain(5)}}
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment