From c2343ca162d10bc0a47a0281a80ced415c0d7809 Mon Sep 17 00:00:00 2001 From: Greg Brimble Date: Thu, 3 Oct 2024 13:31:15 -0400 Subject: [PATCH] Remove custom ports known issue (#17306) --- .../docs/workers/platform/known-issues.mdx | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/src/content/docs/workers/platform/known-issues.mdx b/src/content/docs/workers/platform/known-issues.mdx index 705fb8a0071521b..ce25a4cf3130cb6 100644 --- a/src/content/docs/workers/platform/known-issues.mdx +++ b/src/content/docs/workers/platform/known-issues.mdx @@ -81,22 +81,6 @@ After adding `sub2.example.com` to Cloudflare DNS // -> Can be resolved by Fetch API ``` -## Custom ports - -For Workers subrequests, when a Worker is deployed, custom ports are ignored and requests are sent to the scheme's default port, such as `443` for HTTPS. Note that when developing a Worker locally, or from within the Cloudflare dashboard using Quick Edit, custom ports are respected and allowed. - -For example: - -```js -await fetch('https://example.com:1234/foo') -``` - -is the equivalent of: - -```js -await fetch('https://example.com/foo') -``` - ## Fetch to IP addresses For Workers subrequests, requests can only be made to URLs, not to IP addresses directly. To overcome this limitation [add a A or AAAA name record to your zone](https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/) and then fetch that resource.