Is Date.now() frozen from the first time it's called, or as soon as JS starts executing?

Ddave Is Date.now() frozen from the first time it's called, or as soon as JS starts ex...

H

Hello, I’m Allie!•5/23/23, 7:58 PM

Second option

Kkrondor Is there a timeline for this?

D

daveOP•5/23/23, 8:54 PM

Our AWS server/services implementations are currently closed-source. We haven't started on the vbucket project yet, but it would probably be closed-source too.

(I sadly don't work for Cloudflare, not sure if my Discord role made it look like I do; sorry for the confusion if that's what happened.)

D

daveOP•5/23/23, 11:55 PM

I am probably like one of three people who actually want this feature, but... has there been any mention if we'll be able to upload custom Chromium builds to use with the Workers Browser Rendering API?

For context, one of the side-projects we're working on (for fun) is detecting ITW JavaScript exploits.

D

daveOP•5/23/23, 11:58 PM

oh lol I just realized you folks use HAR files too internally for browser HTTP artifacts.

W

Walshy•5/24/23, 2:25 AM

https://developers.cloudflare.com/browser-rendering/platform/puppeteer/

W

Walshy•5/24/23, 2:26 AM

You couldn't use puppeteer out of the box, but, we have support for it using Browser Workers!

D

divby0•5/24/23, 8:25 AM

What would be the best approach to return one answer for a request immediately and then after an external api has answered return another answer? Without workers, I'd probably use server-sent-events + an event emitter but I am not sure that this is the serverless way

M

manstfu•5/24/23, 8:53 AM

someone know what is this?

NNeo Is Cloudflare Workers good for making an API server?

C

Cyb3r-Jak3•5/24/23, 11:14 AM

I mean depends on what your API server needs to do. If simple requests handling then sure

B

banbanboi•5/24/23, 12:32 PM

how to fix cors issue when consuming the worker url? it works in a plain get, but if i include a header key value in the request, it throws the Cors error. i also provided the correct cors response

Bbanbanboi how to fix cors issue when consuming the worker url? it works in a plain get, bu...

H

Hello, I’m Allie!•5/24/23, 12:34 PM

Do you also return CORS headers on

OPTIONS

OPTIONS

OPTIONS

OPTIONS requests?

HHello, I’m Allie!Do you also return CORS headers on `OPTIONS` requests?

B

banbanboi•5/24/23, 12:35 PM

no, for now I only use Get, post

Bbanbanboi no, for now I only use Get, post

H

Hello, I’m Allie!•5/24/23, 12:35 PM

That might be why. Your browser may be sending a preflight

OPTIONS

OPTIONS

OPTIONS

OPTIONS request, which fails.

HHello, I’m Allie!That might be why. Your browser may be sending a preflight `OPTIONS` request, wh...

B

banbanboi•5/24/23, 12:38 PM

i removed it including the Head, but still the same

Here's what my Web looks like when calling the worker url

Bbanbanboi i removed it including the Head, but still the same Here's what my Web looks l...

H

Hello, I’m Allie!•5/24/23, 12:39 PM

No, I mean that your browser itself is sending an

OPTIONS

OPTIONS

OPTIONS

OPTIONS request, irrespective of your

Access-Control-Allow-Methods

Access-Control-Allow-Methods

Access-Control-Allow-Methods

Access-Control-Allow-Methods. If you don't handle that in your Worker, then the entire thing fails

HHello, I’m Allie!No, I mean that your browser itself is sending an `OPTIONS` request, irrespectiv...

B

banbanboi•5/24/23, 12:41 PM

no options sent by the browser

B

banbanboi•5/24/23, 12:41 PM

during request

NNeo I was thinking about using Workers to build an API for a timetabling app that wi...

C

Cyb3r-Jak3•5/24/23, 1:35 PM

Workers scale very easily not sure about Fauna DB but if it does then it should be good

NNeo What about GraphQL, does that work with Workers?

C

Cyb3r-Jak3•5/24/23, 2:06 PM

https://github.com/cloudflare/workers-graphql-server

GitHub

GitHub - cloudflare/workers-graphql-server: 🔥Lightning-fast, global...

Lightning-fast, globally distributed Apollo GraphQL server, deployed at the edge using Cloudflare Workers - GitHub - cloudflare/workers-graphql-server:

Lightning-fast, globally distributed Apollo...

GitHub - cloudflare/workers-graphql-server: 🔥Lightning-fast, global...

I

IdkWhatever69•5/24/23, 2:50 PM

am i doing something wrong?

I

IdkWhatever69•5/24/23, 2:50 PM

cron triggers dont work

I

IdkWhatever69•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

IdkWhatever69•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?

Is Date.now() frozen from the first time it's called, or as soon as JS starts executing?

Similar Threads

Similar Threads

Similar Threads