https://developers.cloudflare.com/workers/platform/changelog/#2021-01-14

F

Francisco•1/14/24, 1:25 AM

Thanks! I will try this

UUnsmart https://developers.cloudflare.com/workers/platform/changelog/#2021-01-14

F

Francisco•1/14/24, 1:28 AM

Shouldn't this information be here? https://developers.cloudflare.com/workers/runtime-apis/

Runtime APIs · Cloudflare Workers docs

The Workers runtime is designed to be JavaScript standards compliant and web-interoperable. Wherever possible, it uses web platform APIs, so that code …

K

kian•1/14/24, 1:32 AM

Most of the globals/APIs you get from browsers aren't documented but are just available

F

Francisco•1/14/24, 1:36 AM

Oh cool, I came here to ask about the Files API because I couldn't find it on that page

R

ramesh prasad•1/14/24, 3:57 AM

I have an usecase to cover. After every 1000 worker invocation I need to hit an api to external system. how can i do that? Any idea on this? Workers will as usual get data from user, the data will be stored on lets say d1. And after 1000 data I get from user, I need to push that data to external system. Any idea here?

G

Gunnar•1/14/24, 11:43 AM

Wow, debugging a CF Worker (typescript) in WebStorm for the first time is pretty powerful!

https://blog.cloudflare.com/debugging-cloudflare-workers

The Cloudflare Blog

Better debugging for Cloudflare Workers, now with breakpoints

We provide many tools to help you debug Cloudflare Workers; from your local environment all the way into production. In this post, we highlight some of the tools we currently offer, and do a deep dive into one specific area - breakpoint debugging - a tool we recently added into our workerd runtime.

Ɽ

ⱤØ₥₳₦•1/14/24, 2:36 PM

How to cache range request in cloudflare worker?

GGunnar Wow, debugging a CF Worker (typescript) in WebStorm for the first time is pretty...

S

sathoro•1/14/24, 3:27 PM

coming from Notepad, that's crazy

ⱤⱤØ₥₳₦How to cache range request in cloudflare worker?

Ɽ

ⱤØ₥₳₦•1/14/24, 4:49 PM

ⱤⱤØ₥₳₦🥴🥴🥲

C

Cyb3r-Jak3•1/14/24, 7:53 PM

I believe the cache API respects the range header so should match the headers on

match

match

match

match.

D

dave•1/14/24, 8:22 PM

What happens if I use the cache-control request header and

cacheEverything: true

cacheEverything: true

cacheEverything: true

cacheEverything: true?

U

UnsmartOP•1/14/24, 8:30 PM

Yeah all cache everything does is allow caching all requests regardless of the extension. It will use the cache headers unless you specifically tell it to use a certain ttl

M

MarkB•1/14/24, 11:45 PM

Hello, when I selected ssl encryption mode as Flexible, it gives unknown web server error (520 error).
with Full mode, it works well, please let me know what is wrong

Original message was deleted

M

MarkB•1/15/24, 12:05 AM

you recommend to use Full at least? with even free ssl

Original message was deleted

M

MarkB•1/15/24, 12:07 AM

I have only free ssl, so I am going to use flexible mode, Full with letsencrypt ssl is better than Flexible?

Original message was deleted

M

MarkB•1/15/24, 12:08 AM

got it, thank you

S

Steve Xuereb•1/15/24, 10:21 AM

Hello folks, I'm using

resolveOverride

resolveOverride

resolveOverride

resolveOverride from

RequestInitCfProperties

RequestInitCfProperties

RequestInitCfProperties

RequestInitCfProperties (https://developers.cloudflare.com/workers/runtime-apis/request/#requestinitcfproperties) so that I can proxy the request to specific domains. However it seems like this only works when deploying the workers, and doesn't seem to work with

npx wrangler dev

npx wrangler dev

npx wrangler dev

npx wrangler dev. Is there a way to make it work?

Request · Cloudflare Workers docs

Interface that represents an HTTP request.

F

frekw•1/15/24, 12:50 PM

What parts of the ECMA Script standard do Workers support?

I'm running into some problems with

WeakRef

WeakRef

WeakRef

WeakRef and

FinalizationRegistry

FinalizationRegistry

not being available, which it should be according to the spec https://262.ecma-international.org/14.0/#sec-weak-ref-objects

Unfortunately I don't have that much control over the code since it's outputted by a WASM compiler :/

A

Advany•1/15/24, 12:52 PM

My workers (on a paid plan) are being rate limited. I tried to check for waf events for that zone... with rule id worker or action equals block. I dont see that but users are reporting 1015.

Where can I find the rate limiting events of my worker?

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

Advany•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!

https://developers.cloudflare.com/workers/platform/changelog/#2021-01-14

Similar Threads