Fetch ignoring port about workers-sdk HOT 13 CLOSED

We're going to close this for now as it's dependent on internal Cloudflare changes. For now, fetch ignoring custom ports is considered behaviour as designed, but that may be revisited in the future. Of note—you should be able to make fetch requests to a custom port within your own Cloudflare zone.

from workers-sdk.

Let's leave this open till we ship a fix in the runtime

from workers-sdk.

Whoops, reopening

from workers-sdk.

For whomever this may help:

I recently had this issue and ended up using AWS API Gateway as a http proxy to forward requests to the custom port origin. It took only a few clicks and meant that I could continue using workers as usual. It costs pennies per month and its Edge optimised as well.

from workers-sdk.

hi all 👋 we see this issue has been re-opened. however, we have discussed again internally and can confirm this behavior is a consequence of the interaction between the workers runtime and the rest of cloudflare's systems and isn't related to wrangler, so we are going to re-close the issue. however, there is an open internal ticket to track this: EW-1281. we note that there is not currently a timeline on this, and it's not on the immediate roadmap for the relevant team.

@codenoid in terms of a fetch to a custom port on your own cloudflare zone (see https://developers.cloudflare.com/fundamentals/setup/accounts-and-zones/#zones for reference), this won't work in wrangler dev, but will work when your worker is deployed to the cloudflare network 👍

from workers-sdk.

This issue has been automatically marked as stale because it has not had recent activity in the last 180 days. It will be closed if no further activity occurs in the next week. Please feel free to comment if you'd like it to remain open, and thank you for your contributions.

from workers-sdk.

Please keep this open

from workers-sdk.

@threepointone can you reopen this? I think the release notes closed it

from workers-sdk.

I think maybe this fix broke running the wrangler dev server if you are using Yarn 3 PnP? From version 2.0.16 and onwards I now get the following error when I try to start the dev server with yarn wrangler dev:

X [ERROR] Could not read from file: D:\Code\Cloudflare\Test\.yarn\cache\wrangler-npm-2.0.16-25a529adf2-67d437092c.zip\node_modules\wrangler\templates\checked-fetch.js


X [ERROR] Build failed with 1 error:

  error: Could not read from file:
  D:\Code\Cloudflare\Test\.yarn\cache\wrangler-npm-2.0.16-25a529adf2-67d437092c.zip\node_modules\wrangler\templates\checked-fetch.js

from workers-sdk.

Good catch! Fix incoming.

from workers-sdk.

@jfsiii has this been fixed?

from workers-sdk.

Recently, fetch() seems to start respecting custom port in deployment. Maybe they have fixed this in the runtime. Can anybody confirm? Custom port is respected only when fetch's URL shares the same second-level domain with the worker's custom domain.

from workers-sdk.

"you should be able to make fetch requests to a custom port within your own Cloudflare zone"

sorry, but wdym by that?

from workers-sdk.