My workers (on a paid plan) are being rate limited. I tried to check for waf events for that zone...

SSteve Xuereb Hello folks, I'm using `resolveOverride` from `RequestInitCfProperties` (https:/...

E

Erisa•1/15/24, 2:26 PM

Try using wrangler dev --remote which runs the worker on the real edge using your zone configuration

AAdvany My workers (on a paid plan) are being rate limited. I tried to check for waf eve...

E

Erisa•1/15/24, 2:27 PM

Hey, this limit is the abuse protection mentioned here https://developers.cloudflare.com/workers/platform/limits/#request
but it isn't meant to interrupt real traffic and Support can remove the limit if you open a ticket requesting it.

E

Erisa•1/15/24, 2:28 PM

They should show up in events view though! That's strange

V

vakno•1/15/24, 2:53 PM

Hey i am new to cloudflare and workers. I want to implement schema markup for FaqElement via cloudflare worker.
I made a worker that has hardcoded script like this.

const schemaMarkup = {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
            {
                "@type": "Question",
                "name": "What is Lorem Ipsum?",
                "acceptedAnswer": {
                    "@type": "Answer",
                    "text": "answer"
                }
            },
            {
                "@type": "Question",
                "name": "Why do we use it?",
                "acceptedAnswer": {
                    "@type": "Answer",
                    "text": "answer 2"
                }
            },
            {
                "@type": "Question",
                "name": "Where does it come from?",
                "acceptedAnswer": {
                    "@type": "Answer",
                    "text": "answer 3"
                }
            }
            // Add more FAQ items as needed
        ]
    };

const schemaMarkup = {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
            {
                "@type": "Question",
                "name": "What is Lorem Ipsum?",
                "acceptedAnswer": {
                    "@type": "Answer",
                    "text": "answer"
                }
            },
            {
                "@type": "Question",
                "name": "Why do we use it?",
                "acceptedAnswer": {
                    "@type": "Answer",
                    "text": "answer 2"
                }
            },
            {
                "@type": "Question",
                "name": "Where does it come from?",
                "acceptedAnswer": {
                    "@type": "Answer",
                    "text": "answer 3"
                }
            }
            // Add more FAQ items as needed
        ]
    };

const schemaMarkup = {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
            {
                "@type": "Question",
                "name": "What is Lorem Ipsum?",
                "acceptedAnswer": {
                    "@type": "Answer",
                    "text": "answer"
                }
            },
            {
                "@type": "Question",
                "name": "Why do we use it?",
                "acceptedAnswer": {
                    "@type": "Answer",
                    "text": "answer 2"
                }
            },
            {
                "@type": "Question",
                "name": "Where does it come from?",
                "acceptedAnswer": {
                    "@type": "Answer",
                    "text": "answer 3"
                }
            }
            // Add more FAQ items as needed
        ]
    };

const schemaMarkup = {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
            {
                "@type": "Question",
                "name": "What is Lorem Ipsum?",
                "acceptedAnswer": {
                    "@type": "Answer",
                    "text": "answer"
                }
            },
            {
                "@type": "Question",
                "name": "Why do we use it?",
                "acceptedAnswer": {
                    "@type": "Answer",
                    "text": "answer 2"
                }
            },
            {
                "@type": "Question",
                "name": "Where does it come from?",
                "acceptedAnswer": {
                    "@type": "Answer",
                    "text": "answer 3"
                }
            }
            // Add more FAQ items as needed
        ]
    };

My question is if i can tell worker to set answers and questions dynamically from HTML (from class name for example), i cant seem to find an option inside HTMLRewriter class.

EErisa They should show up in events view though! That's strange

A

AdvanyOP•1/15/24, 2:57 PM

yeah. already send a support message... I can't find them in the events view

Vvakno Hey i am new to cloudflare and workers. I want to implement schema markup for Fa...

Z

zegevlier•1/15/24, 3:21 PM

Also posted in workers-and-pages-helpI want to implement schema markup for FaqElement via cloudflare. Please post your question only in a single channel

D

davelongdev•1/15/24, 4:38 PM

hi - trying to set up worker to send an email and getting

✘ [ERROR] service core:user:test: Uncaught Error: No such module "cloudflare-internal:email".

✘ [ERROR] service core:user:test: Uncaught Error: No such module "cloudflare-internal:email".

✘ [ERROR] service core:user:test: Uncaught Error: No such module "cloudflare-internal:email".

✘ [ERROR] service core:user:test: Uncaught Error: No such module "cloudflare-internal:email".

D

davelongdev•1/15/24, 4:38 PM

any ideas?

A

Arma•1/15/24, 6:23 PM

I ran into the same issue the other day

A

Arma•1/15/24, 6:23 PM

https://community.cloudflare.com/t/bad-docs-typeerror-when-sending-an-email-from-a-worker/600433

A

Arma•1/15/24, 6:24 PM

Basically "cloudflare-internal:email" does not work on miniflare (yet)

A

Arma•1/15/24, 6:24 PM

but does work when deployed

D

davelongdev•1/15/24, 6:25 PM

i've been using

npx wrangler dev  --remote

npx wrangler dev  --remote

npx wrangler dev  --remote

npx wrangler dev  --remote

which seems to be working

D

davelongdev•1/15/24, 6:27 PM

i'm getting two emails now for some reason though. not sure why.

A

Arma•1/15/24, 6:28 PM

Do you query the endpoint with your browser? if that's the case, maybe it's the favicon request

D

davelongdev•1/15/24, 6:29 PM

i don't think so?

D

davelongdev•1/15/24, 6:30 PM

i'm just trying to follow this tutorial https://developers.cloudflare.com/email-routing/email-workers/send-email-workers/

Send emails from Workers · Cloudflare Email Routing docs

You can send an email about your Worker’s activity from your Worker to an email address verified on Email Routing. This is useful for when you want to …

D

davelongdev•1/15/24, 6:30 PM

i just deploy the worker from wrangler, start the dev server, and then open a browser window using the dev tools

A

Arma•1/15/24, 6:32 PM

Look at the network tab of your browser, you should see 2 requests. From your description it definitely sounds like the browser is invoking the worker twice

A

Arma•1/15/24, 6:32 PM

which is fine

A

Arma•1/15/24, 6:33 PM

your worker need to check the path that is requested, and not send the email for any random path

D

davelongdev•1/15/24, 6:34 PM

yeah looks like maybe it's the favicon

Screen_Shot_2024-01-15_at_1.34.40_PM.png

A

Arma•1/15/24, 6:37 PM

export default {
  async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
    const path = new URL(request.url).pathname
    if (path == '/send-email') {
        // your email code...
    }

export default {
  async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
    const path = new URL(request.url).pathname
    if (path == '/send-email') {
        // your email code...
    }

export default {
  async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
    const path = new URL(request.url).pathname
    if (path == '/send-email') {
        // your email code...
    }

export default {
  async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
    const path = new URL(request.url).pathname
    if (path == '/send-email') {
        // your email code...
    }

A

Arma•1/15/24, 6:37 PM

you would do something like this

A

Arma•1/15/24, 6:38 PM

or better yet, use a router like

itty-router

itty-router

itty-router

itty-router to define your endpoints

D

davelongdev•1/15/24, 6:39 PM

ok thanks. just learning how to use all of this, so trying to figure it all out.

A

Arma•1/15/24, 6:39 PM

glad to help

A

Arma•1/15/24, 6:41 PM

By the way, you can send a response immediatedly and do the slow email sending in the background

A

Arma•1/15/24, 6:42 PM

by using

context.waitUntil()

context.waitUntil()

context.waitUntil()

context.waitUntil()

D

davelongdev•1/15/24, 6:43 PM

thanks!

X

xap3y•1/15/24, 8:51 PM

I have this code in my email worker:

await fetch("http://example.host.site", {
    method: "POST",
    headers: {
    "Content-Type": "application/json;charset=UTF-8",
    },
    body: JSON.stringify(data),
});

await message.forward("myMainEmail@gmail.com");

await fetch("http://example.host.site", {
    method: "POST",
    headers: {
    "Content-Type": "application/json;charset=UTF-8",
    },
    body: JSON.stringify(data),
});

await message.forward("myMainEmail@gmail.com");

await fetch("http://example.host.site", {
    method: "POST",
    headers: {
    "Content-Type": "application/json;charset=UTF-8",
    },
    body: JSON.stringify(data),
});

await message.forward("myMainEmail@gmail.com");

await fetch("http://example.host.site", {
    method: "POST",
    headers: {
    "Content-Type": "application/json;charset=UTF-8",
    },
    body: JSON.stringify(data),
});

await message.forward("myMainEmail@gmail.com");

When I send email from my gmail i send it to the

myMainEmail@gmail.com

myMainEmail@gmail.com

myMainEmail@gmail.com

myMainEmail@gmail.com but doesnt post the request to the host, but when I trigger email with that test tool, it send the post request. Im new to workers so I dont really know

D

davelongdev•1/15/24, 11:31 PM

why is the syntax different in wrangler than in the gui?

K

kian•1/15/24, 11:38 PM

What are you referring to specifically?

D

davelongdev•1/15/24, 11:59 PM

the content of the index.js file in the project folder is different than what shows up in the index.js file in the gui (quick edit) after you deploy it?

D

davelongdev•1/15/24, 11:59 PM

for workers

D

davelongdev•1/16/24, 12:00 AM

@kian

K

kian•1/16/24, 12:06 AM

Wrangler uses esbuild to bundle your Worker, they're functionally equivalent though.

D

davelongdev•1/16/24, 12:08 AM

maybe that's part of it but i'm also seeing two different syntax approaches - service workers and es modules?

K

kian•1/16/24, 12:08 AM

You can do either with Wrangler and the dashboard.

K

kian•1/16/24, 12:08 AM

Service Workers are legacy and use

addEventListener

addEventListener

addEventListener

addEventListener

K

kian•1/16/24, 12:08 AM

Module Workers are the recommended syntax and use

export default

export default

export default

export default

D

davelongdev•1/16/24, 12:09 AM

hrm - i was having an issue using service workers in wrangler so i thought i had to switch it to es modules

D

davelongdev•1/16/24, 12:10 AM

maybe i just had a bug or something ; maybe a cache issue?

D

davelongdev•1/16/24, 12:10 AM

thanks

D

davelongdev•1/16/24, 12:41 AM

i pasted my worker from the dashboard into wrangler and i'm getting a cors error. can't call the worker at all

D

davelongdev•1/16/24, 12:42 AM

maybe i'm missing something idk . ah - i think i need to move the linked kv namespace

D

davelongdev•1/16/24, 1:12 AM

that didn't work :/

My workers (on a paid plan) are being rate limited. I tried to check for waf events for that zone...

Similar Threads

Similar Threads

Similar Threads