Yeah so each invocation has the same limit but you can invoke a worker from another worker to get an

D

dave•1/31/24, 1:12 AM

you could even make a simple Worker that just takes in a list of URLs, and returns a list of responses from each lol

E

ErisaOP•1/31/24, 1:13 AM

As an aside you can also make a Worker have a service binding of itself

EErisa Yeah so each invocation has the same limit but you can invoke a worker from anot...

D

dave•1/31/24, 1:14 AM

if you go down through only 3 subrequests, aren't you already allowed to make 1 trillion requests? (1000 * 1000 * 1000 * 1000)

E

ErisaOP•1/31/24, 1:15 AM

In theory yes but in practice you may find yourself falling victim to anti abuse systems if you try to launch 1 trillion subrequests

D

dave•1/31/24, 1:18 AM

hah I would expect to be blocked at that scale anyway

D

dave•1/31/24, 1:20 AM

the cost for 1 trillion subrequests in this example would be $300 right? (1000 * 1000 * 1000) * (0.30/1,000,000)

Ddave the cost for 1 trillion subrequests in this example would be $300 right? (1000 *...

S

Sam•1/31/24, 8:31 AM

Shouldn't you also count in cpu time?

V

vakno•1/31/24, 9:24 AM

Why is this not working on /rewrite.html i get 404 error

export default {
  async fetch(request, env, ctx) {
    let response = await fetch(request)

    // Check if the request URL ends with "test.html"
      // Create a new response with the same content but a different URL
      const newUrl = request.url.replace('/test.html', '/rewrite.html')
      console.log(newUrl)
      response = new Response(response.body, {
        status: 301, // Redirect status code
        headers: {
          ...response.headers,
          'Location': newUrl
        }
      })
    
  
    return response
  },
};

export default {
  async fetch(request, env, ctx) {
    let response = await fetch(request)

    // Check if the request URL ends with "test.html"
      // Create a new response with the same content but a different URL
      const newUrl = request.url.replace('/test.html', '/rewrite.html')
      console.log(newUrl)
      response = new Response(response.body, {
        status: 301, // Redirect status code
        headers: {
          ...response.headers,
          'Location': newUrl
        }
      })
    
  
    return response
  },
};

export default {
  async fetch(request, env, ctx) {
    let response = await fetch(request)

    // Check if the request URL ends with "test.html"
      // Create a new response with the same content but a different URL
      const newUrl = request.url.replace('/test.html', '/rewrite.html')
      console.log(newUrl)
      response = new Response(response.body, {
        status: 301, // Redirect status code
        headers: {
          ...response.headers,
          'Location': newUrl
        }
      })
    
  
    return response
  },
};

export default {
  async fetch(request, env, ctx) {
    let response = await fetch(request)

    // Check if the request URL ends with "test.html"
      // Create a new response with the same content but a different URL
      const newUrl = request.url.replace('/test.html', '/rewrite.html')
      console.log(newUrl)
      response = new Response(response.body, {
        status: 301, // Redirect status code
        headers: {
          ...response.headers,
          'Location': newUrl
        }
      })
    
  
    return response
  },
};

K

kian•1/31/24, 9:33 AM

What's the route on the Worker?

V

vakno•1/31/24, 9:40 AM

domainname/test.html

V

vakno•1/31/24, 9:40 AM

it is changing the url but i get 404 error on page

K

kian•1/31/24, 9:43 AM

The Worker isn't involved with /rewrite.html if you don't have a route covering that, so the 404 isn't an issue from the Worker.

V

vakno•1/31/24, 10:00 AM

What do you mean by that?

V

vakno•1/31/24, 10:03 AM

I want to achieve changing url from /test.html to /rewrite.html but serving the same content

Vvakno What do you mean by that?

H

Hello, I’m Allie!•1/31/24, 10:04 AM

Workers are given certain routes on which they operate. If the route does not include /rewrite.html, then it will not be involved in serving the request

HHello, I’m Allie!Workers are given certain routes on which they operate. If the route does not in...

V

vakno•1/31/24, 10:07 AM

but why is there a need for /rewrite.html route? By my understanding i only need route /test.html

V

vakno•1/31/24, 10:08 AM

If i will set both routes for this worker there will be redirect loop

Vvakno I want to achieve changing url from /test.html to /rewrite.html but serving the ...

K

kian•1/31/24, 10:09 AM

That’s not what you’re doing, you’re redirecting them to the new page

Kkian That’s not what you’re doing, you’re redirecting them to the new page

V

vakno•1/31/24, 10:11 AM

yes and serving response of trigger route

K

kian•1/31/24, 10:11 AM

On the new page, the Worker isn’t being hit.

V

vakno•1/31/24, 10:12 AM

what do i need to change?

K

Kitodi•1/31/24, 11:33 AM

Does anybody uses TCP Stream in cloudflare workers, when I try to run

read()

read()

read()

read() without server response it got stuck? #TCP Sockets read() function got stuck

K

Kitodi•1/31/24, 11:47 AM

Is it considered a bug or can it be prevented if it happens?

R

Rapid•1/31/24, 11:58 AM

Is there a way to tell cloudflare where I want the worker to work? (certain region instead of close to my region)

R

Rapid•1/31/24, 11:59 AM

More specifically for Workers Routes to leverage API speed from my servers which reside in n.virginia

R

Rapid•1/31/24, 12:00 PM

I feel like if I my worker goes from my location to NVirginia instead of NVirginia worker goes directly to nvirginia and then sends me the results, nvirginia worker would be fatster

RRapid More specifically for Workers Routes to leverage API speed from my servers which...

H

Hello, I’m Allie!•1/31/24, 12:01 PM

That sounds like Smart Placement. You aren't able to manually tell it where to spawn the Worker, but it should automatically determine which colo to spawn in to get itself closest to your origin(s)

R

Rapid•1/31/24, 12:01 PM

By default, Workers and Pages Functions are invoked in a data center closest to where the request was received. If you are running back-end logic in a Worker, it may be more performant to run that Worker closer to your back-end infrastructure rather than the end user. Smart Placement automatically places your workloads in an optimal location that minimizes latency and speeds up your applications.

By default, Workers and Pages Functions are invoked in a data center closest to where the request was received. If you are running back-end logic in a Worker, it may be more performant to run that Worker closer to your back-end infrastructure rather than the end user. Smart Placement automatically places your workloads in an optimal location that minimizes latency and speeds up your applications.

By default, Workers and Pages Functions are invoked in a data center closest to where the request was received. If you are running back-end logic in a Worker, it may be more performant to run that Worker closer to your back-end infrastructure rather than the end user. Smart Placement automatically places your workloads in an optimal location that minimizes latency and speeds up your applications.

By default, Workers and Pages Functions are invoked in a data center closest to where the request was received. If you are running back-end logic in a Worker, it may be more performant to run that Worker closer to your back-end infrastructure rather than the end user. Smart Placement automatically places your workloads in an optimal location that minimizes latency and speeds up your applications.

R

Rapid•1/31/24, 12:02 PM

So the worker is indeed doing some back-end logic in the worker, that's the reason I want it to be spawned close to the server

R

Rapid•1/31/24, 12:02 PM

Is it possible to see logs of my latest worker runs? to know wher eit was spawned?

RRapid Is it possible to see logs of my latest worker runs? to know wher eit was spawne...

H

Hello, I’m Allie!•1/31/24, 12:06 PM

You could

console.log

console.log

the

request.cf.colo

request.cf.colo

request.cf.colo

request.cf.colo field, then view it in live logs/

wrangler tail

wrangler tail

?

R

Rapid•1/31/24, 12:10 PM

I'm seeing real-time logs and I can see it

R

Rapid•1/31/24, 12:10 PM

so, it does it in France (FRA) as it seems

R

Rapid•1/31/24, 12:10 PM

and I need it to be around NVirginia, you think I should enable Smart Placements?

K

kian•1/31/24, 12:11 PM

Smart Placement is automatic and runs it based on where the RTT would be lowest based on your subrequests - if you make enough subrequests to a server there, it'll put it closer to there

R

Rapid•1/31/24, 12:11 PM

okay checking it now

SSam Shouldn't you also count in cpu time?

D

dave•1/31/24, 1:56 PM

I'm assuming each subrequest takes less than 30ms of CPU time

D

dave•1/31/24, 1:56 PM

oh wait

D

dave•1/31/24, 1:56 PM

it would be clocked as if it was one request

D

dave•1/31/24, 1:56 PM

...weird.

C

Chaika•1/31/24, 4:10 PM

When a user sends a request, they get routed to a specific machine in a specific colocation/datacenter in a specific PoP. That machine/metal spins up an isolate for your worker, which has its own memory. Connection keepalive will keep them connected to the same metal for a bit, so you might see it "working" and using your in-memory objects repeatedly, but any other client/new connection would be randomly routed to a different machine
https://developers.cloudflare.com/workers/reference/how-workers-works/

How Workers works · Cloudflare Workers docs

The difference between the Workers runtime versus traditional browsers and Node.js.

C

Chaika•1/31/24, 4:11 PM

Not even cache is per PoP, it's per colo/datacenter. Some PoPs like ORD are made up of mutiple colos each with their own cache (called multi-colo pops, MCPs)

C

Chaika•1/31/24, 4:14 PM

but yea the guarantee is really only per request

Isolates are resilient and continuously available for the duration of a request, but in rare instances isolates may be evicted.

Even if they connect to the same metal/machine I believe, they might connect to a different isolate

Because there is no guarantee that any two user requests will be routed to the same or a different instance of your Worker, Cloudflare recommends you do not use or mutate global state.

quotes from: https://developers.cloudflare.com/workers/reference/how-workers-works/

C

Chaika•1/31/24, 4:14 PM

You can use the Cache API to get per-colo cache
https://developers.cloudflare.com/workers/runtime-apis/cache/

Yeah so each invocation has the same limit but you can invoke a worker from another worker to get an

Similar Threads

Similar Threads

Similar Threads