cron triggers dont work

I

IdkWhatever69OP•5/24/23, 2:51 PM

Bbanbanboi no options sent by the browser

S

sathoro•5/24/23, 2:52 PM

if you are doing a CORS request, your browser is automatically sending an OPTIONS request

CCyb3r-Jak3 I mean depends on what your API server needs to do. If simple requests handling ...

S

sathoro•5/24/23, 2:53 PM

Workers is only for "simple requests"?

IIdkWhatever69 cron triggers dont work

I

IdkWhatever69OP•5/24/23, 3:08 PM

anyone? please help

Ssathoro Workers is only for "simple requests"? 🙂

B

banbanboi•5/24/23, 3:08 PM

so having a key value request header will not work?
i put the worker key value in querystring, does this workaround is the best practice ?
does jwt will also work or I will be having a CORS issue once I implement it?

Bbanbanboi so having a key value request header will not work? i put the worker key value ...

S

sathoro•5/24/23, 3:08 PM

you just need to implement CORS correctly. you aren't even handling the CORS preflight request so of course it won't work

S

sathoro•5/24/23, 3:11 PM

personally I call this function on all responses before returning them to the client:

const enableCORS = (request, response) => {
  const origin = request.headers.get("origin") || "";

  const isAllowedOrigin =
    origin === "http://localhost:3000" ||
    origin.endsWith(".example.com");

  if (isAllowedOrigin) {
    for (const [key, value] of Object.entries({
      "Access-Control-Allow-Origin": origin,
      "Access-Control-Allow-Methods": "POST, DELETE, GET, OPTIONS",
      "Access-Control-Allow-Headers": "*",
    })) {
      response.headers.append(key, value);
    }
  }

  return response;
};

const enableCORS = (request, response) => {
  const origin = request.headers.get("origin") || "";

  const isAllowedOrigin =
    origin === "http://localhost:3000" ||
    origin.endsWith(".example.com");

  if (isAllowedOrigin) {
    for (const [key, value] of Object.entries({
      "Access-Control-Allow-Origin": origin,
      "Access-Control-Allow-Methods": "POST, DELETE, GET, OPTIONS",
      "Access-Control-Allow-Headers": "*",
    })) {
      response.headers.append(key, value);
    }
  }

  return response;
};

const enableCORS = (request, response) => {
  const origin = request.headers.get("origin") || "";

  const isAllowedOrigin =
    origin === "http://localhost:3000" ||
    origin.endsWith(".example.com");

  if (isAllowedOrigin) {
    for (const [key, value] of Object.entries({
      "Access-Control-Allow-Origin": origin,
      "Access-Control-Allow-Methods": "POST, DELETE, GET, OPTIONS",
      "Access-Control-Allow-Headers": "*",
    })) {
      response.headers.append(key, value);
    }
  }

  return response;
};

const enableCORS = (request, response) => {
  const origin = request.headers.get("origin") || "";

  const isAllowedOrigin =
    origin === "http://localhost:3000" ||
    origin.endsWith(".example.com");

  if (isAllowedOrigin) {
    for (const [key, value] of Object.entries({
      "Access-Control-Allow-Origin": origin,
      "Access-Control-Allow-Methods": "POST, DELETE, GET, OPTIONS",
      "Access-Control-Allow-Headers": "*",
    })) {
      response.headers.append(key, value);
    }
  }

  return response;
};

and in my route handling I have a simple

if (request.method === "OPTIONS") {
  return new Response("ok");
}

if (request.method === "OPTIONS") {
  return new Response("ok");
}

if (request.method === "OPTIONS") {
  return new Response("ok");
}

if (request.method === "OPTIONS") {
  return new Response("ok");
}

and this is what ties it together...

const response = await handleRequest(request, env, context, sentry);

return enableCORS(request, response);

const response = await handleRequest(request, env, context, sentry);

return enableCORS(request, response);

const response = await handleRequest(request, env, context, sentry);

return enableCORS(request, response);

const response = await handleRequest(request, env, context, sentry);

return enableCORS(request, response);

Ssathoro you just need to implement CORS correctly. you aren't even handling the CORS pre...

B

banbanboi•5/24/23, 3:14 PM

thank you can I try this ?

Bbanbanboi thank you can I try this ?

S

sathoro•5/24/23, 3:15 PM

yeah go for it

Ssathoro Workers is only for "simple requests"? 🙂

C

Cyb3r-Jak3•5/24/23, 3:38 PM

I mean no heavy compute or long requests

CCyb3r-Jak3 I mean no heavy compute or long requests

S

sathoro•5/24/23, 3:39 PM

we do several minute long requests it works fine actually

S

sathoro•5/24/23, 3:39 PM

the client just needs to stay connected lol

S

sathoro•5/24/23, 3:40 PM

using SSE

K

kian•5/24/23, 3:42 PM

What's your Worker code?

NNeo Is Cloudflare Workers good for making an API server?

D

dave•5/24/23, 3:48 PM

all of our public facing API services are on Cloudflare Workers, and even most of the private APIs are also on Workers.

KKartik ```app.get("*", async (ctx) => { const cacheurl = new URL(ctx.req.url); // c...

K

kian•5/24/23, 3:49 PM

headers

headers

is always going to be blank other than

pix-api

pix-api

pix-api

pix-api in that scenario.

K

kian•5/24/23, 3:50 PM

You're not using the request headers, you define

headers

headers

with

let headers = new Headers();

let headers = new Headers();

let headers = new Headers();

let headers = new Headers(); which is an empty object and then only contains the

pix-api

pix-api

pix-api

pix-api header which you set.

K

kian•5/24/23, 3:50 PM

If you want to use the request headers, that'd be

ctx.req.headers

ctx.req.headers

ctx.req.headers

ctx.req.headers

T

tobi•5/24/23, 4:07 PM

hi

with the upcoming workers snippets, in theory i should be able to make a "free" load balancer for an api; and the only real limit should be the dns resolution fees, is that correct (which only start at 1m/month)?

K

kian•5/24/23, 4:11 PM

Snippets can only make 1 subrequest so you wouldn't be able to do that.

K

kian•5/24/23, 4:11 PM

Well, you can do Math.random and select a subdomain based on that

K

kian•5/24/23, 4:11 PM

but you wouldn't be able to hit one and then decide to fallback if it failed

N

Neiki•5/24/23, 4:44 PM

can i somehow send me an email or sending with an webhook if that happens again? like let me notify

NNeiki can i somehow send me an email or sending with an webhook if that happens again?...

N

Neiki•5/24/23, 4:56 PM

i cant find anything to workers or crons in the notifications tab, only about pages

Kkian Well, you can do Math.random and select a subdomain based on that

T

tobi•5/24/23, 5:04 PM

yeah, fallback would not be a possibility. but i could do either random, or based on some "hash" of the request ip + maybe some user cookie or sth.

T

tobi•5/24/23, 5:07 PM

@kiannh then, if 1 request can be split to multiple subdomains, one could assign only functioning servers to those subdomains, i.e. if i know one of my servers is down, i change its subdomain to point to a known good server

T

tobi•5/24/23, 5:08 PM

one thing i had in mind was sending ppl to "local" servers; i.e. near their closest cf-POP. i hope this will be possible with snippets

Ttobi hi 😄 with the upcoming workers snippets, in theory i should be able to make a ...

D

dave•5/24/23, 5:28 PM

Is your API HTTP already?

T

tobi•5/24/23, 5:31 PM

yea

Ttobi yea

D

dave•5/24/23, 5:35 PM

you can already do multiple fetches in parallel and just race to the first one that completes.

T

tobi•5/24/23, 5:35 PM

hmm... doesn't seem like an elegant solution.

D

dave•5/24/23, 5:35 PM

sure it is

T

tobi•5/24/23, 5:36 PM

if i have lets say 5 servers then i get 5x the traffic with this method

T

tobi•5/24/23, 5:37 PM

yea, basically just "forwarding" the request somewhere, right?

Ttobi if i have lets say 5 servers then i get 5x the traffic with this method

D

dave•5/24/23, 5:37 PM

Sure, but you can cache the result too if it's problem.

T

tobi•5/24/23, 5:38 PM

depends on what one wants to accomplish.

D

dave•5/24/23, 5:38 PM

It's really nice since you can do "advanced" ish load balancing too if want.

e.g. can see the round-trip latency by doing:

curl -s "https://untrusted.files.ai.moda/api/v1.0.0-alpha/ping" | jq

curl -s "https://untrusted.files.ai.moda/api/v1.0.0-alpha/ping" | jq

curl -s "https://untrusted.files.ai.moda/api/v1.0.0-alpha/ping" | jq

curl -s "https://untrusted.files.ai.moda/api/v1.0.0-alpha/ping" | jq

T

tobi•5/24/23, 5:39 PM

if i, lets say want to build some kind of "low-latency" storage for small files, that is kinda guaranteed to have sub <50-60 ms latency, i could make that with less (or no) js on the user side, while still being able to serve the data quickly.

Similar Threads

Similar Threads

Similar Threads