How a replication PutObject that carries Object Lock parameters satisfies
the target-side rule that such a request must also carry Content-MD5 or
an x-amz-checksum-* header (AWS S3, MinIO and most compatible stores
enforce it; rustfs#7082).
Fail-closed decision for an SSE-C passthrough replication attempt, derived
from the target’s cached SsecPassthroughCapability. Pure so the policy
can migrate with the worker (M2) without dragging the cache along; the
caller computes expired from the cache record’s age (see the runtime’s
SSEC_PASSTHROUGH_CAPABILITY_TTL).
Whether the ETag the target returned for a single-part replica proves the
stored bytes differ from what the source sent — e.g. a target that does not
decode aws-chunked framing stores the frames verbatim and returns their
ETag. Only a plain single-part MD5 ETag on both sides is decidable; a
multipart or opaque (encrypted) ETag, or a withheld replica ETag, returns
false because no corruption can be concluded from it.
True when a replication-check HEAD of the replica proves the SSE-C
material survived passthrough: a RustFS target restores the transport
headers into the stored SSE-C keys and its HEAD echoes
x-amz-server-side-encryption-customer-algorithm (the replication-check
exemption skips key validation but not the metadata echo). A target that
dropped the headers stored a plain object and echoes nothing. The caller
extracts the echoed customer-algorithm value from its HEAD response type.
Judge the identity contract from one replication write: None when no
contract applies (the source addressed no real version — an empty or nil
uuid travels as the literal “null”, unversioned-source semantics),
otherwise whether the target echoed the source id or answered with
anything else — including nothing at all.
Runtime half of the P1-19 version-identity contract (the explicit probe
lives in replication-check’s VersionFidelity phase): every replication PUT
response reveals whether the target adopted the source version id. A
target minting its own ids silently breaks version-addressed deletes and
heal, so surface it — once per target — instead of letting the divergence
accumulate unseen.
Pure drift judgment: the contract only applies when the source addressed a
real (non-nil) version uuid, and drift means the target answered with
anything else — including nothing at all.