// AI Platform Drift
Cloudflare Gateway can now forward traffic to Workers for transformation
Cloudflare developer changelog · published 2026-10-15 21:25 UTC
WHAT CHANGEDCloudflare Gateway added a Forward action in HTTP policies that routes matching traffic to Workers, available in public beta as of 15 October 2026 on all Zero Trust plans. Workers receive the request plus Gateway context including connection metadata, user identity, and device posture. Gateway evaluates HTTP request policies before Forward policies and inspects responses before returning them to users.
WHY IT MATTERSIf you use Cloudflare Gateway for outbound traffic inspection, you can now intercept and transform requests to AI APIs without deploying a separate proxy. This enables request/response logging to R2, prompt filtering, or response modification inline with your existing Gateway policies. Gateway still handles TLS decryption and body inspection, so a Block decision on the original request body can interrupt the Worker.
WHAT TO DOReview your Gateway HTTP policies to determine whether any traffic you currently block or allow would benefit from transformation or logging. If so, deploy a Worker using one of Cloudflare's templates and configure a Forward policy to route that traffic through it.
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
+## Cloudflare One, Workers, Gateway - Gateway and Workers integration is now in public beta +https://developers.cloudflare.com/changelog/post/2026-10-15-gateway-workers-public-beta/ +Thu, 15 Oct 2026 00:00:00 GMT + +Cloudflare Gateway now integrates with Cloudflare Workers in public beta on all Zero Trust plans. You can use the Forward action in Gateway HTTP policies to run your own code on matching, permitted traffic without managing a separate proxy. +The Forward action lets you transform HTTP requests and responses, return a coaching page, or run background tasks such as Slack notifications and R2 captures. Your Worker receives the request and Gateway context, including connection metadata, user identity, and device posture when available. + +Gateway handles the proxy connection, TLS decryption, and upstream routing. It evaluates HTTP request policies before Forward policies and inspects the final response before returning it to the user. +Gateway inspects the original request body before delivering it to your Worker. A body-inspection Block decision can interrupt the Worker. +To get started, deploy a Worker and configure a Forward policy, or adapt one of the Worker templates.
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 | New public beta integration between Gateway and Workers adds execution capability and changes deployment model for teams using Zero Trust. |
| signals | new integration feature announced · public beta launch date (2026-10-15) · new API capability (Forward action in Gateway HTTP policies) · security/execution model change (Workers can now intercept and transform Gateway traffic) · deployment workflow change (Workers + Gateway policies required) |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |