From 98f3038fc48a6db5890b1f4bbc76f359392dcfc6 Mon Sep 17 00:00:00 2001 From: Mike Nomitch Date: Mon, 19 May 2025 09:28:45 -0700 Subject: [PATCH] Documents connect being shut off when outbound worker is used --- .../configuration/outbound-workers.mdx | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers.mdx b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers.mdx index d78ba5d85db639e..340cec9d969aec1 100644 --- a/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers.mdx +++ b/src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers.mdx @@ -18,6 +18,13 @@ Outbound Workers can be used to: * Create, allow, or block lists for hostnames requested by user Workers. * Configure authentication to your APIs behind the scenes (without end developers needing to set credentials). +:::note + +When an Outbound Worker is enabled, your customer's Worker will no longer be able to use the [`connect() API`](/workers/runtime-apis/tcp-sockets/#connect) +to create outbound TCP Sockets. This is to ensure all outbound communication goes through the Outbound Worker's `fetch` method. + +::: + ## Use Outbound Workers To use Outbound Workers: