CD
Cloudflare Developers•13mo ago
jasonkuhrt

Worker A binding to Worker B leads to `403` error upon runtime fetch call. Why?

I have two works, A & B, A binds to B. When A does the env.BINDING.fetch(...) call it leads to a 403 response. That response is NOT coming from our code. Why is CF doing this? The body response is: error code: 1003
2 Replies
jasonkuhrt
jasonkuhrt•13mo ago
jasonkuhrt
jasonkuhrt•13mo ago
Never mind, I wasn't calling correctly the fetch from the binding. ☑️
Want results from more Discord servers?
Add your server
More Posts
Middleware OK on `pages.dev`, not on custom domain?I tried `_middleware.js` stuff with CF Pages, in an attempt to use it instead of an existing CF WorkZero Trust doesnt route real DomainHello, I have in my internal Network in the hosts file a hostname with the following domain satowa-Where can I find TypeScript type definitions of `@cloudflare/workers-types` pkg in Github?Where can I find TypeScript type definitions of `@cloudflare/workers-types` pkg in Github?Connecting to CockroachDB serverless using pg via workers1. Created a npx wrangler init . 2. Then "npm install pg" and added the query code into index.js 3. Custom workers domains outside domain zoneHey there, one of the products my company develops utilizes workers, however we want to use our ClouCloudflare Pages incorrect node versionHi! I have my environment variable set to `NODE_VERSION=18` in the Pages configuration, however, it