From 53baebacc93503e872db51fe88b068ba5514ea6d Mon Sep 17 00:00:00 2001
From: Quanah Gibson-Mount <quanah@openldap.org>
Date: Tue, 30 Sep 2008 19:50:04 +0000
Subject: [PATCH] ITS#5718
---
CHANGES | 3 ++-
doc/guide/admin/overlays.sdf | 14 ++++++++++++++
2 files changed, 16 insertions(+), 1 deletion(-)
diff --git a/CHANGES b/CHANGES
index 72bd44e1e0..855c54a2ad 100644
--- a/CHANGES
+++ b/CHANGES
@@ -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)
diff --git a/doc/guide/admin/overlays.sdf b/doc/guide/admin/overlays.sdf
index 48dd94d02a..8987caa462 100644
--- a/doc/guide/admin/overlays.sdf
+++ b/doc/guide/admin/overlays.sdf
@@ -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)}}
--
GitLab