// AI Platform Drift
Workers subrequests to BYOIP destinations now preserve context
Cloudflare developer changelog · published 2026-10-31 17:22 UTC
WHAT CHANGEDCloudflare now preserves Workers context when a subrequest targets a Cloudflare-proxied hostname using Bring Your Own IP (BYOIP). Workers subrequests to BYOIP destinations now preserve the CF-Worker header and cf.worker.upstream_zone field. Cross-zone requests now set CF-Connecting-IP to the fixed Workers client IP address 2a06:98c0:3600::103 instead of the original client IP. Bot Management fields on the destination zone now represent the original end-user connection instead of the internal Cloudflare connection.
WHY IT MATTERSSecurity rules that previously evaluated internal Cloudflare connections will now evaluate the original client, changing which requests pass or fail. Bot Management scores, verified bot status, and JA3/JA4 fingerprints will change for affected BYOIP subrequests. Cross-zone subrequests that relied on CF-Connecting-IP containing the client IP will now receive a fixed internal IP address instead.
WHAT TO DOReview security rules and Bot Management configurations that apply to Workers subrequests targeting BYOIP destinations. Test cross-zone subrequests that depend on CF-Connecting-IP to confirm they handle the fixed internal IP 2a06:98c0:3600::103 correctly.
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-30-byoip-workers-subrequest-context/ +Fri, 30 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. +Because Cloudflare-proxied BYOIP destinations now follow standard Workers subrequest handling, cross-zone requests set CF-Connecting-IP to the Workers client IP address 2a06:98c0:3600::103 for security reasons. This applies when a Worker in one Cloudflare zone sends a subrequest to a hostname in another Cloudflare zone. Same-zone subrequests continue to reflect the client IP through CF-Connecting-IP. +For more information, refer to Cloudflare BYOIP, Workers subrequests, and CF-Connecting-IP in Worker subrequests.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.5 |
|---|---|
| triage reasoning | Breaking changes to Workers subrequest context preservation, Bot Management field semantics, and CF-Connecting-IP behavior affecting security rules and cross-zone requests. |
| signals | breaking behavior change: Workers subrequests to BYOIP destinations now preserve context (previously lost) · security rule evaluation change: CF-Worker header and cf.worker.upstream_zone now preserved · Bot Management field semantics changed: scores now represent original end-user, not internal connection · CF-Connecting-IP behavior change: cross-zone requests now set to fixed internal IP (2a06:98c0:3600::103) instead of client IP · bug fix with side effects: false 403 responses previously returned, now corrected · authentication/context preservation: meaningful change to how Workers identify and evaluate traffic |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |