# Workers, BYOIP, Bots - Workers subrequests now preserve context for BYOIP destinations

Publisher-attributed story with a reviewed brief or permitted publisher paragraph. The original publisher is responsible for the linked reporting.

- Publisher: Cloudflare Developers
- Category: Cloud
- Original publication time: 2026-10-30T00:00:00Z
- First observed by NexusTechWire: 2026-10-30T10:50:40Z
- Original source: https://developers.cloudflare.com/changelog/post/2026-10-30-byoip-workers-subrequest-context/
- NexusTechWire record: https://nexustechwire.com/news/news-5188503ee440c242a40d

## From the publisher

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.

Source license: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Publisher excerpt shortened and converted to plain text. Original source license applies.

Read the full original: [Cloudflare Developers](https://developers.cloudflare.com/changelog/post/2026-10-30-byoip-workers-subrequest-context/)

This record does not reproduce the complete article or represent independent confirmation of every source claim.
