Cloudflare Developers•12mo ago

Worker to Worker fetch

Hi there, I would like to ask for some help with my cloudflare worker. When i make a request to another cloudflare worker of mine that holds a variable with data in it from another cloudflare worker. The data returned is empty, however i make the data request from my browser or api tester, it returns the correct data. It is specifcally when I request the data from a cloudflare worker.

import { Router } from 'itty-router'; const router = Router()

order_data = [];

//admin only
router.get("/order", async (req) => {
   return new Response(JSON.stringify(order_data));
});

import { Router } from 'itty-router'; const router = Router()

order_data = [];

//admin only
router.get("/order", async (req) => {
   return new Response(JSON.stringify(order_data));
});

72 Replies

McSneaky•12mo ago

Apparently you can't do workers-to-workers fetch. You have to use service binding: https://developers.cloudflare.com/workers/configuration/bindings/about-service-bindings/

Service bindings - Configuration · Cloudflare Workers docs

Service bindings are an API that facilitate Worker-to-Worker communication via explicit bindings defined in your configuration.

Erisa•12mo ago

That's correct, the Workers either have to be on separate Cloudflare zones (e.g. example.com, example.net and example.workers.dev are all separate zones) or use Service Bindings Service Bindings is the recommended solution

Mr. GoodmanOP•12mo ago

my workers are on seperate cloudflare zones, however it still cannot return the information correctly

Erisa•12mo ago

What do you get back exactly?

Mr. GoodmanOP•11mo ago

a json containing order data @Erisa | Support Engineer its here in the code I provided thats the cloudflare worker that hold the data

export const order_management = {
    async postData(data) {
        return await(await fetch(
            `https://server.syntaxrecoveriesorders.workers.dev/order/${encodeURIComponent(JSON.stringify(data))}`, { method: "POST" }
        )).text();
    },
    async getData(id) {
        return await(await fetch(
            `https://server.syntaxrecoveriesorders.workers.dev/order/${encodeURIComponent(id)}`
        )).text();
    }
}

export const order_management = {
    async postData(data) {
        return await(await fetch(
            `https://server.syntaxrecoveriesorders.workers.dev/order/${encodeURIComponent(JSON.stringify(data))}`, { method: "POST" }
        )).text();
    },
    async getData(id) {
        return await(await fetch(
            `https://server.syntaxrecoveriesorders.workers.dev/order/${encodeURIComponent(id)}`
        )).text();
    }
}

this is how i get data from it @Erisa | Support Engineer

kian•11mo ago

What URL is the Worker that has this code?

Mr. GoodmanOP•11mo ago

the one i sent now? @kian https://server.syntaxrecoveriesorders.workers.dev https://manager.syntaxrecoveries.workers.dev/ @kian anyone?

McSneaky•11mo ago

server.syntaxrecoveriesorders.workers.dev and server.syntaxrecoveriesorders.workers.dev Are both on the same zone, so you can't make requests between them. You have to use service binding

Mr. GoodmanOP•11mo ago

@McSneaky bro ready their not the same @Erisa | Support Engineer can u both read their not .syntaxrecoveriesorders .syntaxrecoveries

McSneaky•11mo ago

Aah, I was looking at your code example.. I assume everything under workers.dev need to use service binding tho But that would be security issue, if they are all the same and can bind like that Try to put one under your custom domain and keep other under workers.dev

Mr. GoodmanOP•11mo ago

Can u help me with how service bindings work? @McSneaky how do i communicate to server

McSneaky•11mo ago

Worker 1 called "MY_SERVICE_TO_CALL":

import { Router } from 'itty-router'; const router = Router()

order_data = [];

//admin only
router.get("/order", async (req) => {
   return new Response(JSON.stringify(order_data));

import { Router } from 'itty-router'; const router = Router()

order_data = [];

//admin only
router.get("/order", async (req) => {
   return new Response(JSON.stringify(order_data));

Worker 2:

router.get("/other-endpoint", async (req, env) => {
   return env.MY_BINDING.fetch(`http://MY_SERVICE_TO_CALL/order/${encodeURIComponent(id)}`, request)
}

router.get("/other-endpoint", async (req, env) => {
   return env.MY_BINDING.fetch(`http://MY_SERVICE_TO_CALL/order/${encodeURIComponent(id)}`, request)
}

And inside your wrangler.toml of Worker 2 define BINDING and SERVICE in services

services = [
  { binding = "MY_BINDING", service = "MY_SERVICE_TO_CALL" },
]

services = [
  { binding = "MY_BINDING", service = "MY_SERVICE_TO_CALL" },
]

That service has to be other worker name https://discord.com/channels/595317990191398933/1193924170749317161/1193924170749317161 Learned it yesterday 😅

Mr. GoodmanOP•11mo ago

@McSneaky what is MY_SERVICE_TO_CALL services = [ { binding = "server", service = "server.syntaxrecoveries.workers.dev" }, ]?

McSneaky•11mo ago

It's your worker name

Mr. GoodmanOP•11mo ago

server? can i get an example?

McSneaky•11mo ago

Worker

Mr. GoodmanOP•11mo ago

no bro example of the name wym by name please

McSneaky•11mo ago

What's the name of your other worker to call You can check it's name from other worker wrangler.toml or from CloudFlare dashboard

Mr. GoodmanOP•11mo ago

server its called server

McSneaky•11mo ago

Aah, thought you have literal server, like VPS 😅

Mr. GoodmanOP•11mo ago

services = [
  { binding = "server", service = "server" },
]

services = [
  { binding = "server", service = "server" },
]

McSneaky•11mo ago

Then yeah, "server" in your case 👍

Mr. GoodmanOP•11mo ago

lol 🫶

McSneaky•11mo ago

Then env.server.fetch('https://server/orders/10') Something like this should work for you

Mr. GoodmanOP•11mo ago

how do you get env if its not a request? like if i want to postData just as a function not in a route i need env still

McSneaky•11mo ago

Most likely need to pass it to that function

Mr. GoodmanOP•11mo ago

i dont think i can its hard to explain

McSneaky•11mo ago

export const order_management = {
    async postData(data, env) {
      env.server.fetch(...)
    },
    async getData(id, env) {
    }
}
// And then use in your worker as 
router.get("/other-endpoint", async (req, env) => {
    await order_management.postData(data, env)
}

export const order_management = {
    async postData(data, env) {
      env.server.fetch(...)
    },
    async getData(id, env) {
    }
}
// And then use in your worker as 
router.get("/other-endpoint", async (req, env) => {
    await order_management.postData(data, env)
}

Mr. GoodmanOP•11mo ago

no im not using router.get like where do i get env from without getting it from router oh wait lmao nvm sorry im dumb also error code: 1042 https://server.syntaxrecoveriesorders.workers.dev/order

McSneaky•11mo ago

https://developers.cloudflare.com/workers/runtime-apis/service-bindings#interface It's also 2nd arg in there

Service bindings - Runtime APIs · Cloudflare Workers docs

Facilitate Worker-to-Worker communication.

McSneaky•11mo ago

Replace all that https://server.syntaxrecoveriesorders.workers.dev/order With just https://server/order

Mr. GoodmanOP•11mo ago

no something is wrong can i show u in a screenshare? i did in my code

McSneaky•11mo ago

Hmm.. Then maybe it works differently in workers.dev 🤔 I was using on actual domain

Mr. GoodmanOP•11mo ago

im getting error 1101

McSneaky•11mo ago

No idea what that is

Mr. GoodmanOP•11mo ago

internal service error

McSneaky•11mo ago

No idea what that is either 😄

Mr. GoodmanOP•11mo ago

on my manager worker

router.get("/order/:id", async (req, env) => {
  return new Response(await order_management.getData(decodeURIComponent(req.params.id),env));
})

router.get("/order/:id", async (req, env) => {
  return new Response(await order_management.getData(decodeURIComponent(req.params.id),env));
})

export const order_management = {
    async postData(data) {
        return await(await fetch(
            `https://server.syntaxrecoveriesorders.workers.dev/order/${encodeURIComponent(JSON.stringify(data))}`, { method: "POST" }
        )).text();
    },
    async getData(id,env) {
        return await(await env.server.fetch(
            `http://server/order/${encodeURIComponent(id)}`
        )).text();
    }
}

export const order_management = {
    async postData(data) {
        return await(await fetch(
            `https://server.syntaxrecoveriesorders.workers.dev/order/${encodeURIComponent(JSON.stringify(data))}`, { method: "POST" }
        )).text();
    },
    async getData(id,env) {
        return await(await env.server.fetch(
            `http://server/order/${encodeURIComponent(id)}`
        )).text();
    }
}

🥺 looks good to me idk why its throwing an error im using getData btw just for now

McSneaky•11mo ago

Yeah, looks good You can try to wrap some try-catches in there or .catch()'es where to log out errors See maybe there's something more useful than just that error code

Mr. GoodmanOP•11mo ago

router.get("/order/:id", async (req, env) => {
  try {
     return new Response(await order_management.getData(decodeURIComponent(req.params.id),env));
  } catch(error) {
     return new Response(error)
  }
})

router.get("/order/:id", async (req, env) => {
  try {
     return new Response(await order_management.getData(decodeURIComponent(req.params.id),env));
  } catch(error) {
     return new Response(error)
  }
})

TypeError: Cannot read properties of undefined (reading 'order_server')

TypeError: Cannot read properties of undefined (reading 'order_server')

export const order_management = {
    async postData(data) {
        return await(await fetch(
            `https://server.syntaxrecoveriesorders.workers.dev/order/${encodeURIComponent(JSON.stringify(data))}`, { method: "POST" }
        )).text();
    },
    async getData(id,env) {
        return await(await env.order_server.fetch(
            `http://order_server/order/${encodeURIComponent(id)}`
        )).text();
    }
}

export const order_management = {
    async postData(data) {
        return await(await fetch(
            `https://server.syntaxrecoveriesorders.workers.dev/order/${encodeURIComponent(JSON.stringify(data))}`, { method: "POST" }
        )).text();
    },
    async getData(id,env) {
        return await(await env.order_server.fetch(
            `http://order_server/order/${encodeURIComponent(id)}`
        )).text();
    }
}

McSneaky•11mo ago

env is undefined?!

Mr. GoodmanOP•11mo ago

yerr lmao

McSneaky•11mo ago

Eeee 😅 How so 🤔

Mr. GoodmanOP•11mo ago

idk

McSneaky•11mo ago

You are using that itty-router?

Mr. GoodmanOP•11mo ago

positive

McSneaky•11mo ago

No idea.. That's what I have Worker 1 called "edge-encoder":

// worker.toml
name = "edge-encoder"
main = "index.js"
compatibility_date = "2022-05-03"

services = [
  { binding = "collector", service = "edge-collector-dev" },
]

// worker.toml
name = "edge-encoder"
main = "index.js"
compatibility_date = "2022-05-03"

services = [
  { binding = "collector", service = "edge-collector-dev" },
]

// .js
import { Router } from 'itty-router';

// Create a new router
const router = Router();

router.get('/edge/encoder/v1', async ({ query }, env) => {
  let base64 = btoa(JSON.stringify(query));
  return env.collector.fetch('https://edge-collector-dev/edge/collector/v1?encoded_object=' + base64)
})

// .js
import { Router } from 'itty-router';

// Create a new router
const router = Router();

router.get('/edge/encoder/v1', async ({ query }, env) => {
  let base64 = btoa(JSON.stringify(query));
  return env.collector.fetch('https://edge-collector-dev/edge/collector/v1?encoded_object=' + base64)
})

Worker 2 called "edge-collector-dev":

// .js
import { Router } from 'itty-router';

// Create a new router
const router = Router();

router.get('/edge/collector/v1', async ({ query }, env) => {
  console.log(query)
  return new Response('OK')
})

// .js
import { Router } from 'itty-router';

// Create a new router
const router = Router();

router.get('/edge/collector/v1', async ({ query }, env) => {
  console.log(query)
  return new Response('OK')
})

Works perfectly 🤔 No idea why env is undefined for you And what are those odd error codes you got

Mr. GoodmanOP•11mo ago

McSneaky•11mo ago

Log out env in router to see if it exists there

Mr. GoodmanOP•11mo ago

what?

McSneaky•11mo ago

router.get("/order/:id", async (req, env) => {
  console.log(env) // What does it say?
  try {
     return new Response(await order_management.getData(decodeURIComponent(req.params.id),env));
  } catch(error) {
     return new Response(error)
  }
})

router.get("/order/:id", async (req, env) => {
  console.log(env) // What does it say?
  try {
     return new Response(await order_management.getData(decodeURIComponent(req.params.id),env));
  } catch(error) {
     return new Response(error)
  }
})

Aah, are you running on local with dev? Service binding might work only in prod Have to wrangler deploy and then test in prod 😋

McSneaky•11mo ago

Mr. GoodmanOP•11mo ago

idk what ur saying im new to cloudflare workers

McSneaky•11mo ago

How are you running your test env? wrangler dev? npm run dev?

Mr. GoodmanOP•11mo ago

PS E:\Desktop\Syntax Recoveries Manager> wrangler dev
 ⛅️ wrangler 3.7.0 (update available 3.22.3)
------------------------------------------------------
wrangler dev now uses local mode by default, powered by 🔥 Miniflare and 👷 workerd.
To run an edge preview session for your Worker, use wrangler dev --remote
▲ [WARNING] Processing wrangler.toml configuration:

    - "services" fields are experimental and may change or break at any time.


▲ [WARNING] This worker is bound to live services: order_server (server)


▲ [WARNING] Enabling Node.js compatibility mode for built-ins and globals. This is experimental and has serious tradeoffs. Please see https://github.com/ionic-team/rollup-plugin-node-polyfills/ for more details.


Your worker has access to the following bindings:
- Services:
  - order_server: server
▲ [WARNING] ⎔ Support for service bindings in local mode is experimental and may change.


⎔ Starting local server...
kj/async-io-win32.c++:982: warning: Bind address resolved to multiple addresses.  Only the first address will be used.  If this is incorrect, specify the address numerically.  This may be fixed in the future.; addrs[0].toString() = 127.0.0.1:63121
[mf:inf] Ready on http://0.0.0.0:8787 
[mf:inf] - http://10.0.0.6:8787
[mf:inf] - http://127.0.0.1:8787
╭───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮│ [b] open a browser, [d] open Devtools, [l] turn off local mode, [c] clear console, [x] to exit                                                                                                            │╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

PS E:\Desktop\Syntax Recoveries Manager> wrangler dev
 ⛅️ wrangler 3.7.0 (update available 3.22.3)
------------------------------------------------------
wrangler dev now uses local mode by default, powered by 🔥 Miniflare and 👷 workerd.
To run an edge preview session for your Worker, use wrangler dev --remote
▲ [WARNING] Processing wrangler.toml configuration:

    - "services" fields are experimental and may change or break at any time.


▲ [WARNING] This worker is bound to live services: order_server (server)


▲ [WARNING] Enabling Node.js compatibility mode for built-ins and globals. This is experimental and has serious tradeoffs. Please see https://github.com/ionic-team/rollup-plugin-node-polyfills/ for more details.


Your worker has access to the following bindings:
- Services:
  - order_server: server
▲ [WARNING] ⎔ Support for service bindings in local mode is experimental and may change.


⎔ Starting local server...
kj/async-io-win32.c++:982: warning: Bind address resolved to multiple addresses.  Only the first address will be used.  If this is incorrect, specify the address numerically.  This may be fixed in the future.; addrs[0].toString() = 127.0.0.1:63121
[mf:inf] Ready on http://0.0.0.0:8787 
[mf:inf] - http://10.0.0.6:8787
[mf:inf] - http://127.0.0.1:8787
╭───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮│ [b] open a browser, [d] open Devtools, [l] turn off local mode, [c] clear console, [x] to exit                                                                                                            │╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

McSneaky•11mo ago

Yeah, I'm not sure if that that works You might need to deploy both workers with wrangler deploy and then test on production (real URL, not local)

Mr. GoodmanOP•11mo ago

i have been doing that

McSneaky•11mo ago

And then you get same error?

Mr. GoodmanOP•11mo ago

yes

McSneaky•11mo ago

Welp 😐 Then I'm all outta ideas

Mr. GoodmanOP•11mo ago

TypeError: Cannot read properties of undefined (reading 'order_server') TypeError: Cannot read properties of undefined (reading 'order_server') TypeError: Cannot read properties of undefined (reading 'order_server') TypeError: Cannot read properties of undefined (reading 'order_server') so annoyinh @McSneaky

name = "manager"
main = "src/main.js"
compatibility_date = "2022-07-12"
node_compat = true

services = [
  { binding = "order_server", service = "server" },
]

name = "manager"
main = "src/main.js"
compatibility_date = "2022-07-12"
node_compat = true

services = [
  { binding = "order_server", service = "server" },
]

{
  "name": "Syntax Recoveries Manager",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "dependencies": {
        "crypto": "^1.0.1",
        "crypto-js": "^4.2.0",
        "cryptojs": "^2.5.3",
        "decode-uri-component": "^0.4.1",
        "itty-router": "^4.0.25",
        "urldecode": "^1.0.1"
      }
    },
    "node_modules/crypto": {
      "version": "1.0.1",
      "resolved": "https://registry.npmjs.org/crypto/-/crypto-1.0.1.tgz",
      "integrity": "sha512-VxBKmeNcqQdiUQUW2Tzq0t377b54N2bMtXO/qiLa+6eRRmmC4qT3D4OnTGoT/U6O9aklQ/jTwbOtRMTTY8G0Ig==",
      "deprecated": "This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in."
    },
    "node_modules/crypto-js": {
      "version": "4.2.0",
      "resolved": "https://registry.npmjs.org/crypto-js/-/crypto-js-4.2.0.tgz",
      "integrity": "sha512-KALDyEYgpY+Rlob/iriUtjV6d5Eq+Y191A5g4UqLAi8CyGP9N1+FdVbkc1SxKc2r4YAYqG8JzO2KGL+AizD70Q=="
    },
    "node_modules/cryptojs": {
      "version": "2.5.3",
      "resolved": "https://registry.npmjs.org/cryptojs/-/cryptojs-2.5.3.tgz",
      "integrity": "sha512-+rdPl1UCxE8s3R94NNn+zMKOiI4MJ7dyh3X0c5uBL3btDr4zQ6acd7f9mY7Wb5MrccZEi2Rrha3OEtLcc5XXog==",
      "engines": {
        "node": "*"
      }
    },
    "node_modules/decode-uri-component": {
      "version": "0.4.1",
      "resolved": "https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.4.1.tgz",
      "integrity": "sha512-+8VxcR21HhTy8nOt6jf20w0c9CADrw1O8d+VZ/YzzCt4bJ3uBjw+D1q2osAB8RnpwwaeYBxy0HyKQxD5JBMuuQ==",
      "engines": {
        "node": ">=14.16"
      }
    },
    "node_modules/itty-router": {
      "version": "4.0.25",
      "resolved": "https://registry.npmjs.org/itty-router/-/itty-router-4.0.25.tgz",
      "integrity": "sha512-WbH1x46QFKNAjp85GYZzDteriZl9nJ0flwGJDVfzC4HT0B/nb01/KOD7mEr+5cYmuqy9T7L/A3ifNzCpzQ1fcw=="
    },
    "node_modules/urldecode": {
      "version": "1.0.1",
      "resolved": "https://registry.npmjs.org/urldecode/-/urldecode-1.0.1.tgz",
      "integrity": "sha512-h0S6hi8/2kC6ZTbnzRyRC86BKDp9rSV2BndvtedcPSFcWdqdXc2Bru1NuF4Oq89D4HKitpX3+EJDry0uOjfTyw=="
    }
  }
}

{
  "name": "Syntax Recoveries Manager",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "dependencies": {
        "crypto": "^1.0.1",
        "crypto-js": "^4.2.0",
        "cryptojs": "^2.5.3",
        "decode-uri-component": "^0.4.1",
        "itty-router": "^4.0.25",
        "urldecode": "^1.0.1"
      }
    },
    "node_modules/crypto": {
      "version": "1.0.1",
      "resolved": "https://registry.npmjs.org/crypto/-/crypto-1.0.1.tgz",
      "integrity": "sha512-VxBKmeNcqQdiUQUW2Tzq0t377b54N2bMtXO/qiLa+6eRRmmC4qT3D4OnTGoT/U6O9aklQ/jTwbOtRMTTY8G0Ig==",
      "deprecated": "This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in."
    },
    "node_modules/crypto-js": {
      "version": "4.2.0",
      "resolved": "https://registry.npmjs.org/crypto-js/-/crypto-js-4.2.0.tgz",
      "integrity": "sha512-KALDyEYgpY+Rlob/iriUtjV6d5Eq+Y191A5g4UqLAi8CyGP9N1+FdVbkc1SxKc2r4YAYqG8JzO2KGL+AizD70Q=="
    },
    "node_modules/cryptojs": {
      "version": "2.5.3",
      "resolved": "https://registry.npmjs.org/cryptojs/-/cryptojs-2.5.3.tgz",
      "integrity": "sha512-+rdPl1UCxE8s3R94NNn+zMKOiI4MJ7dyh3X0c5uBL3btDr4zQ6acd7f9mY7Wb5MrccZEi2Rrha3OEtLcc5XXog==",
      "engines": {
        "node": "*"
      }
    },
    "node_modules/decode-uri-component": {
      "version": "0.4.1",
      "resolved": "https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.4.1.tgz",
      "integrity": "sha512-+8VxcR21HhTy8nOt6jf20w0c9CADrw1O8d+VZ/YzzCt4bJ3uBjw+D1q2osAB8RnpwwaeYBxy0HyKQxD5JBMuuQ==",
      "engines": {
        "node": ">=14.16"
      }
    },
    "node_modules/itty-router": {
      "version": "4.0.25",
      "resolved": "https://registry.npmjs.org/itty-router/-/itty-router-4.0.25.tgz",
      "integrity": "sha512-WbH1x46QFKNAjp85GYZzDteriZl9nJ0flwGJDVfzC4HT0B/nb01/KOD7mEr+5cYmuqy9T7L/A3ifNzCpzQ1fcw=="
    },
    "node_modules/urldecode": {
      "version": "1.0.1",
      "resolved": "https://registry.npmjs.org/urldecode/-/urldecode-1.0.1.tgz",
      "integrity": "sha512-h0S6hi8/2kC6ZTbnzRyRC86BKDp9rSV2BndvtedcPSFcWdqdXc2Bru1NuF4Oq89D4HKitpX3+EJDry0uOjfTyw=="
    }
  }
}

McSneaky•11mo ago

I have no idea.. env is undefined for you for some reason, but I have no idea why For me it worked outta box ¯\_(ツ)_/¯

Mr. GoodmanOP•11mo ago

@McSneaky

Mr. GoodmanOP•11mo ago

McSneaky•11mo ago

Aah, but you don't have Node env. It's ctx env kinda thingy

Mr. GoodmanOP•11mo ago

@McSneaky do both workers have to be binded?

McSneaky•11mo ago

Nope, only one

Mr. GoodmanOP•11mo ago

can i send u my full code? can someone help pls anyone?

Unsmart•11mo ago

https://developers.cloudflare.com/workers/configuration/bindings/about-service-bindings/ This guide should help you understand service bindings and how to use them.

Service bindings - Configuration · Cloudflare Workers docs

Service bindings are an API that facilitate Worker-to-Worker communication via explicit bindings defined in your configuration.

Mr. GoodmanOP•11mo ago

@Unsmart | Tech debt The issue is that it doesnt work. It literally doesnt work. ive done all that

Unsmart•11mo ago

Did you follow the tutorial exactly in order to create one and understand how it works instead of trying to do it in your own project first? It does indeed work many people use it. If you cant figure it out I highly suggest trying to pay a developer to either do it for you or support you through to understanding how it works 🙂

Mr. GoodmanOP•11mo ago

Hey bro @Unsmart | Tech debt, yeah no i did read it, all is set up perfectly fine. All my code is in the above messages. Like it really has no reason not to work. Because the code of the binded worker is fine, i can sned a request to it on my browser perfectly fine. It just doesnt work with the worker that is binding with it. The issue is my env is undefined... We cant figure out why tho.

Gaming

Programming

Worker to Worker fetch