if you use those you should be fine

(its the same ASN, but different ranges)

(also you can get these programmatically at https://api.cloudflare.com/client/v4/ips )

realllly? Lemme check 😛

some of the warp IPs are very close neighbouring ranges, but I can tell you for sure it wont be within those

ahhhhhhh

yep

very close

The IP list is only the list of IPs that will be making requests on behalf of proxied traffic, doesnt count the ones used for other purposes :P

Is there a response code that will terminate the response from a worker or give no response at all? I swear I remember doing this a long time ago with a status code, but I can't find anything on it.

Actually.. that might have been nginx

Guys, Is it possible to use MongoDB in Workers? Connect directly to the drive?

You're thinking of

499

but that has no effect on CF

Ah, 444 was what I used, but close to the same thing.

I don't suppose there's a way to do the same in a worker?

Nope

It'll always return a Response. Either you do it or in the event of a Worker exception, Cloudflare shows an error page

Yeah the error page is what I'm getting, was trying to not have a default route that just responds to everything possible that I don't handle.

suppose I'll do teapot

Is it possible to use a http proxy for fetch or axios on a worker function?

Not particularly

Like you could have a proxy that works with

https://proxy.example.com?url=google.com

but not one that you connect to over IP

https://www.mongodb.com/developer/products/atlas/cloudflare-worker-rest-api/ ?

You need to use the REST API as workers don't support making socket connections

use something like ScrapingBee

thanks

Hey so i have an question about worker limits i dont really understood, as to my knowledge i can run an worker as long as the client is connected right? f.ex i want or need to run it for 30s but then i saw the CPU limit of 10ms what does that mean? can somebody tell me that. F.ex use case: i upload an file and that needs to be processed for 20s with cloudflare workers will this work with free plan?

It means you can use 10ms of CPU - so it depends what your processing time means

Awaiting a HTTP response for 10 seconds doesn't use CPU, as an example, so that's fine on the free plan.

okay let me know if i got it right my worker would do this: i fetch an api that needs 14 seconds to response = is okay i upload an file to an api that takes 10 seconds = not okay because CPU limit right?