but I'm still able to leverage cloudflare CDN even if the a records are not pointing to it, right?

Yyahiaaboushadi but I'm still able to leverage cloudflare CDN even if the a records are not poin...

I

Yes. The idea is that visitors will hit the Cloudflare CDN, and then the CDN will connect to your server (that's why you had to give Cloudflare the server IPs) and get the content.

I

Isaac McFadyen•8/21/24, 1:19 AM

Visitors should still use the CDN. If you want to confirm that, go to

https://yourdomain.com/cdn-cgi/trace

https://yourdomain.com/cdn-cgi/trace

https://yourdomain.com/cdn-cgi/trace

https://yourdomain.com/cdn-cgi/trace (replace yourdomain.com with your domain)

I

Isaac McFadyen•8/21/24, 1:19 AM

If you see a page of text then it's using the Cloudflare CDN

Y

yahiaaboushadiOP•8/21/24, 1:20 AM

ok, thanks so much @Isaac | YYZ01, EWR01 . You're awesome!

J

jmac•8/21/24, 2:54 AM

Hi all, what section should I post a question about this blog post? (am a beginner so a basic usage question)
https://developers.cloudflare.com/analytics/graphql-api/tutorials/capture-graphql-queries-from-dashboard/
and using curl as the client
https://developers.cloudflare.com/analytics/graphql-api/getting-started/execute-graphql-query/
Thanks!!
ps
I am just trying to get the "Overview" section of a website

I

iluthtaqwim•8/21/24, 4:15 AM

hi

D

delta•8/21/24, 6:24 AM

will serving a lot of binary file allowed if we use cache reserve?

EErisa product teams monitor their product channels, and the community team monitor fea...

D

D5•8/21/24, 12:37 PM

Huge thanks! Hope they hear my feedback!

I've done that: r2

V

Vikash•8/21/24, 12:48 PM

Can I reply to an email later on using the

message.reply()

message.reply()

message.reply()

message.reply() on CF email routing worker ?

It looks like the

message-id

message-id

message-id

message-id is used, so what if I store that in D1 and use it later to create message object and reply ? For example, the docs cover an example of ticket creation, so let's say I want to send reply on same email when ticket is updated/closed.

export default {
  async email(message, env, ctx) {
    const ticket = createTicket(message);
    const msg = createMimeMessage();
    msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
    msg.setSender({ name: "Thank you for your contact", addr: "<SENDER>@example.com" });
    msg.setRecipient(message.from);
    msg.setSubject("Email Routing Auto-reply");
    msg.addMessage({
      contentType: 'text/plain',
      data: `We got your message, your ticket number is ${ ticket.id }`
    });
    const replyMessage = new EmailMessage(
      "<SENDER>@example.com",
      message.from,
      msg.asRaw()
    );
    await message.reply(replyMessage);
  }
}

export default {
  async email(message, env, ctx) {
    const ticket = createTicket(message);
    const msg = createMimeMessage();
    msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
    msg.setSender({ name: "Thank you for your contact", addr: "<SENDER>@example.com" });
    msg.setRecipient(message.from);
    msg.setSubject("Email Routing Auto-reply");
    msg.addMessage({
      contentType: 'text/plain',
      data: `We got your message, your ticket number is ${ ticket.id }`
    });
    const replyMessage = new EmailMessage(
      "<SENDER>@example.com",
      message.from,
      msg.asRaw()
    );
    await message.reply(replyMessage);
  }
}

export default {
  async email(message, env, ctx) {
    const ticket = createTicket(message);
    const msg = createMimeMessage();
    msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
    msg.setSender({ name: "Thank you for your contact", addr: "<SENDER>@example.com" });
    msg.setRecipient(message.from);
    msg.setSubject("Email Routing Auto-reply");
    msg.addMessage({
      contentType: 'text/plain',
      data: `We got your message, your ticket number is ${ ticket.id }`
    });
    const replyMessage = new EmailMessage(
      "<SENDER>@example.com",
      message.from,
      msg.asRaw()
    );
    await message.reply(replyMessage);
  }
}

export default {
  async email(message, env, ctx) {
    const ticket = createTicket(message);
    const msg = createMimeMessage();
    msg.setHeader("In-Reply-To", message.headers.get("Message-ID"));
    msg.setSender({ name: "Thank you for your contact", addr: "<SENDER>@example.com" });
    msg.setRecipient(message.from);
    msg.setSubject("Email Routing Auto-reply");
    msg.addMessage({
      contentType: 'text/plain',
      data: `We got your message, your ticket number is ${ ticket.id }`
    });
    const replyMessage = new EmailMessage(
      "<SENDER>@example.com",
      message.from,
      msg.asRaw()
    );
    await message.reply(replyMessage);
  }
}

C

cetronic•8/21/24, 4:36 PM

hello

E

Ephemeros•8/21/24, 7:06 PM

Howdy :D

B

Blink•8/21/24, 10:17 PM

Any else having issues selecting a free plan for Zerotrust?

P

Ping for toast•8/22/24, 2:57 AM

is the dashboard having issues

PPing for toast is the dashboard having issues

P

Peps•8/22/24, 3:04 AM

what kind of issues are you noticing?

C

Chaika•8/22/24, 3:06 AM

yep api/dash def having issues rn, ouch
Peps is raising, I assume they already know internally though

PPeps what kind of issues are you noticing?

P

Ping for toast•8/22/24, 3:10 AM

I have to reload the page 5 times to get anywhere because most of the time it 401s

P

Peps•8/22/24, 3:10 AM

yeah theres def something up currently

C

Chaika•8/22/24, 3:10 AM

https://www.cloudflarestatus.com/incidents/x54t30777c2q

Cloudflare Dashboard and Cloudflare API service issues

CChaika https://www.cloudflarestatus.com/incidents/x54t30777c2q

P

Ping for toast•8/22/24, 3:12 AM

Hey.. I beat the status page :-)

C

Chaika•8/22/24, 3:13 AM

lol you did, hopefully didn't beat their internal monitoring though, status pages are just slow, approval and whatnot

C

Chaika•8/22/24, 3:14 AM

my silly api stuff started seeing errors at :40 or so

C

Chaika•8/22/24, 3:39 AM

idk about server-side events but you're probably thinking of cpu time limits

C

Chaika•8/22/24, 3:40 AM

yea you have unlimited duration as long as the user stays connected, but only 30s of cpu time on standard max per request. cpu time is only consumed when doing stuff with the cpu though, if you're just awaiting a fetch for example, 0 cpu time

Iiamnotapipe 10 ms, 50ms, 30s

C

Chaika•8/22/24, 3:41 AM

it's 10ms for free and 30s max for standard, the 50ms is for bundled which is mostly gone, all non-ent workers paid got migrated to Standard

C

Chaika•8/22/24, 3:41 AM

of course with standard you pay for cpu time though

C

Chaika•8/22/24, 3:45 AM

https://community.cloudflare.com/t/workers-server-sent-events-server-push/184219/3?u=chaika hmm

but I'm still able to leverage cloudflare CDN even if the a records are not pointing to it, right?

Similar Threads

Similar Threads

Similar Threads