// AI Platform Drift

Workers subrequests to BYOIP destinations now preserve client context

Cloudflare developer changelog · published 2026-10-13 14:15 UTC
WORTH KNOWING VERIFY_ONLY APISECURITY
WHAT CHANGEDCloudflare changed how Workers subrequests behave when targeting Cloudflare-proxied hostnames using Bring Your Own IP (BYOIP). These requests now preserve the CF-Worker header, cf.worker.upstream_zone field, and original client signals including bot scores, verified bot status, and JA3/JA4 fingerprints. Previously, this context was lost and the destination zone saw an internal Cloudflare connection instead of the original end-user. The change is automatic and live as of 13 October 2026.
WHY IT MATTERSSecurity rules and Bot Management configurations that were written to handle the old behavior may now evaluate differently. Rules that previously saw internal Cloudflare traffic will now see the original client, potentially changing which requests pass or fail. False 403 responses that occurred due to lost context will stop appearing, which may surface requests that were previously blocked unintentionally.
WHAT TO DOReview security rules and Bot Management configurations on any zone that receives Workers subrequests via BYOIP. Test that rules evaluating bot scores, JA3/JA4 fingerprints, or the CF-Worker header still produce the intended allow/block decisions now that they see original client data instead of internal connection metadata.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Workers, BYOIP, Bots - Workers subrequests now preserve context for BYOIP destinations
+https://developers.cloudflare.com/changelog/post/2026-10-13-byoip-workers-subrequest-context/
+Tue, 13 Oct 2026 00:00:00 GMT
+
+Cloudflare now preserves Workers context when a subrequest targets a Cloudflare-proxied hostname using Bring Your Own IP (BYOIP). These requests are identified as Cloudflare-to-Cloudflare traffic instead of external Internet traffic.
+Previously, some BYOIP subrequests could lose Workers context and original client signals. This could cause security rules to behave unexpectedly, Bot Management to evaluate an internal Cloudflare connection instead of the original client, or affected requests to return false 403 responses.
+Workers subrequests to BYOIP destinations now preserve the CF-Worker header and cf.worker.upstream_zone field. This supports consistent security rule evaluation across same-zone and cross-zone subrequests.
+Bot Management fields on the destination zone now represent the original end-user connection for affected BYOIP subrequests. Bot scores, verified bot status, and JA3/JA4 fingerprints no longer represent the internal connection between Cloudflare services.
+Customers benefit from consistent security rule evaluation, accurate Bot Management results, and fewer unexpected failures when Workers access BYOIP-backed hostnames. The improvement is automatic and requires no configuration changes.
+For more information, refer to Cloudflare BYOIP and Workers subrequests.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningSubrequest context preservation changes how security rules and Bot Management evaluate traffic, fixing prior false failures.
signalsbreaking behavior change: Workers subrequests to BYOIP destinations now preserve context (previously lost) · security rule evaluation behavior changed · Bot Management field interpretation changed (now represents original end-user, not internal connection) · false 403 responses previously returned are now fixed · CF-Worker header and cf.worker.upstream_zone field now preserved · automatic change requiring no configuration but affecting request evaluation
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)