Hello everyone, I'm looking to implement a caching strategy for my Cloudflare Worker to **optimize t

W

Walshy•9/22/24, 11:35 AM

Let me report to the team

W

Walshy•9/22/24, 11:38 AM

That is indeed a very old binding

N

Nelums•9/22/24, 10:14 PM

Sorry for the question, I was searching for help respect a problem I have with my IP and it seems that Cloudflare is involved, is there a channel where I can get any help with it? or it is mandatory to send an email to the company?

N

Nelums•9/22/24, 10:15 PM

You read my mind sir thanks you

AAndré Hey all, I'd love to learn a bit about the design space of the worker api. Any c...

N

NoGameNoFun•9/23/24, 4:32 AM

what is the status for this synchronous XHRs?

L

Leo_C•9/23/24, 8:31 AM

wired bug, is there a problem with the validation regex???

L

Leo_C•9/23/24, 8:31 AM

L

Leo_C•9/23/24, 8:31 AM

L

Leo_C•9/23/24, 8:34 AM

L

Leo_C•9/23/24, 8:38 AM

This is the UI for worker to add routes.

L

Leo_C•9/23/24, 8:46 AM

L

Leo_C•9/23/24, 9:28 AM

Yes, I can create this route using the API, but not on the UI.

L

Leo_C•9/23/24, 9:57 AM

Odd lengths are allowed, but not even lengths.

A

Ashley•9/23/24, 1:46 PM

Anyone using email workers and seen the catch all status just hang? I set it up just now, and it's "flashing" (the status)... only network request I can see that failed was a 404 to zones/subscriptions but not sure if that'd be used for this.

A

Ashley•9/23/24, 1:47 PM

(If I send emails, they don't bounce, but they also don't trigger my worker)

A

Ashley•9/23/24, 1:50 PM

Ah one did just bounce, but not all of them curiously - the email routing status page says it's synced so it should be routing, but I presume the catch all isn't working due to the flashing loading indicator on the status

A

Ashley•9/23/24, 1:51 PM

Yeah it looks bugged

This isn't the real domain I'm using, but I added a second route and it's just hanging on retrieving the status - the 404 exists on this page, not sure if it's the reason, and it's when it tries to call

https://dash.cloudflare.com/api/v4/zones/xxx/subscription

https://dash.cloudflare.com/api/v4/zones/xxx/subscription

https://dash.cloudflare.com/api/v4/zones/xxx/subscription

https://dash.cloudflare.com/api/v4/zones/xxx/subscription

R

Raymond Camden•9/23/24, 3:05 PM

hey folks. i posted to workers-help, but haven't gotten well, help yet

so trying here. I've got a worker that uses a schedule. locally, it runs just fine. but in production, something weird happens. when it tries to use http to hit an API, it gets a 521 response. now here's the weird thing. i added a fetch() to the code so i could run my worker via the browser. the same network call there works, so its literally just failing when cloudflare executes it on a schedule. it's a bit messy now, but the code is here -https://github.com/cfjedimaster/cloudflareworkers-demos/blob/main/getincidents/src/index.js any ideas?

GitHub

cloudflareworkers-demos/getincidents/src/index.js at main · cfjedim...

Repository for CF Workers demos/examples/etc. Contribute to cfjedimaster/cloudflareworkers-demos development by creating an account on GitHub.

A

azizthewhiz•9/23/24, 3:27 PM

I posted how to update Cloudflare Workers project secrets on git push in my personal LinkedIn and X but figured folks here might benefit as well.

If you’re tired (like I was) of copy-pasting environment secrets and setting them manually via dashboard or wrangler CLI I wrote a git pre-push script that automates that.

Set CL secrets in
```
.env.cloudflare
```
.env.cloudflare
```
.env.cloudflare
```
.env.cloudflare
Create
```
CLOUDFLARE_API_TOKEN
```
CLOUDFLARE_API_TOKEN
```
CLOUDFLARE_API_TOKEN
```
CLOUDFLARE_API_TOKEN
and add it to
```
.env.production
```
.env.production
```
.env.production
```
.env.production
Create
```
env-to-json.sh
```
env-to-json.sh
```
env-to-json.sh
```
env-to-json.sh
that generates
```
secrets.json
```
secrets.json
```
secrets.json
```
secrets.json
Update
```
pre-push
```
pre-push
```
pre-push
```
pre-push
git hook

Now your secrets will update on every git push - no more forgetful copy-pasta.

P.S. #3 is optional if you don't mind storing CL secrets in

secrets.json

secrets.json

secrets.json

secrets.json

C

Corsix👾•9/23/24, 8:47 PM

to have several service bindings to other workers in one worker, what's the correct way of formatting it in toml? nested array? like this?

services = [
  { binding = "WORKER_A", service = "worker-a" }, 
  { binding = "WORKER_B", service = "worker-b" }
]

services = [
  { binding = "WORKER_A", service = "worker-a" }, 
  { binding = "WORKER_B", service = "worker-b" }
]

services = [
  { binding = "WORKER_A", service = "worker-a" }, 
  { binding = "WORKER_B", service = "worker-b" }
]

services = [
  { binding = "WORKER_A", service = "worker-a" }, 
  { binding = "WORKER_B", service = "worker-b" }
]

C

Corsix👾•9/23/24, 8:48 PM

i presume but didn't se any in the documentation about it

HHello, I’m Allie!Maybe try pushing them via a `ReadableStream`?

M

Murder Chicken•9/23/24, 10:01 PM

If we're hitting the RPC argument size limit, what are our options. For instance, if we're dealing with a lot of data that needs to to be sent to a service layer via a binding, are we forced to break the data up to get past this limit. You mentioned

ReadableStream

ReadableStream

ReadableStream

ReadableStream ... is there a way to use this to push large arrays of data as an argument?

M

Mingxi•9/24/24, 1:57 AM

Has anyone encountered this issue? I have a domain name pointing to 192.0.2.1 and it's working fine, but no matter what, I can't find the worker that has this domain name bound to it in the worker section.

Y

Yash Bindal (yB)•9/24/24, 8:20 AM

Hi Is there any way possible to use ipv4 to hit external APi instead of Ipv6

Jjam_zaw Hello everyone, I'm looking to implement a caching strategy for my Cloudflare Wo...

C

chocolatkey•9/24/24, 8:28 AM

I saw this, I think this is worth discussing. I've always wondered when using workers what the closest memcached equivalent is, for when I want to store data in a K/V layout, but I don't care about consistency, replication, reliability etc, I just want to e.g. reduce the amount of requests to a database or storage. I've settled on using the cache API + a local map for now, and it seems to work pretty well. I'm not sure how normal this is, but here's what I do:
helpers:

interface ExpiringValue<T> {
    value: T;
    expires: number;
}

// Cloudflare cache namespaces
export const MY_KV_NAMESPACE = 'myservice.internal/v1'
export const MY_CACHE_NAMESPACE = 'https://' + FLAME_KV_NAMESPACE

// These types let you operate on an in-memory cache stored in a Map

/**
 * Get a value from cache
 * @param store Store to access
 * @param key Lookup key
 * @returns Stored type
 */
export function cget<T>(store: Map<string, ExpiringValue<T>>, key: string): T | undefined {
    const val = store.get(key)
    if (!val) return undefined
    if(val.expires < (Date.now() / 1000)) {
        store.delete(key)
        return undefined
    }
    return val.value
}

/**
 * Store a value in cache
 * @param store Store to access
 * @param key Lookup key
 * @param value Value to store
 * @param ttl Time to live in seconds
 */
export function cset<T>(store: Map<string, ExpiringValue<T>>, key: string, value: T, ttl: number) {
    store.set(key, {
        expires: (Date.now() / 1000) + ttl,
        value
    })
}

/**
 * Delete a value in cache
 * @param store Store to access
 * @param key Lookup key
 */
export function cdel<T>(store: Map<string, ExpiringValue<T>>, key: string) {
    store.delete(key)
}

interface ExpiringValue<T> {
    value: T;
    expires: number;
}

// Cloudflare cache namespaces
export const MY_KV_NAMESPACE = 'myservice.internal/v1'
export const MY_CACHE_NAMESPACE = 'https://' + FLAME_KV_NAMESPACE

// These types let you operate on an in-memory cache stored in a Map

/**
 * Get a value from cache
 * @param store Store to access
 * @param key Lookup key
 * @returns Stored type
 */
export function cget<T>(store: Map<string, ExpiringValue<T>>, key: string): T | undefined {
    const val = store.get(key)
    if (!val) return undefined
    if(val.expires < (Date.now() / 1000)) {
        store.delete(key)
        return undefined
    }
    return val.value
}

/**
 * Store a value in cache
 * @param store Store to access
 * @param key Lookup key
 * @param value Value to store
 * @param ttl Time to live in seconds
 */
export function cset<T>(store: Map<string, ExpiringValue<T>>, key: string, value: T, ttl: number) {
    store.set(key, {
        expires: (Date.now() / 1000) + ttl,
        value
    })
}

/**
 * Delete a value in cache
 * @param store Store to access
 * @param key Lookup key
 */
export function cdel<T>(store: Map<string, ExpiringValue<T>>, key: string) {
    store.delete(key)
}

interface ExpiringValue<T> {
    value: T;
    expires: number;
}

// Cloudflare cache namespaces
export const MY_KV_NAMESPACE = 'myservice.internal/v1'
export const MY_CACHE_NAMESPACE = 'https://' + FLAME_KV_NAMESPACE

// These types let you operate on an in-memory cache stored in a Map

/**
 * Get a value from cache
 * @param store Store to access
 * @param key Lookup key
 * @returns Stored type
 */
export function cget<T>(store: Map<string, ExpiringValue<T>>, key: string): T | undefined {
    const val = store.get(key)
    if (!val) return undefined
    if(val.expires < (Date.now() / 1000)) {
        store.delete(key)
        return undefined
    }
    return val.value
}

/**
 * Store a value in cache
 * @param store Store to access
 * @param key Lookup key
 * @param value Value to store
 * @param ttl Time to live in seconds
 */
export function cset<T>(store: Map<string, ExpiringValue<T>>, key: string, value: T, ttl: number) {
    store.set(key, {
        expires: (Date.now() / 1000) + ttl,
        value
    })
}

/**
 * Delete a value in cache
 * @param store Store to access
 * @param key Lookup key
 */
export function cdel<T>(store: Map<string, ExpiringValue<T>>, key: string) {
    store.delete(key)
}

interface ExpiringValue<T> {
    value: T;
    expires: number;
}

// Cloudflare cache namespaces
export const MY_KV_NAMESPACE = 'myservice.internal/v1'
export const MY_CACHE_NAMESPACE = 'https://' + FLAME_KV_NAMESPACE

// These types let you operate on an in-memory cache stored in a Map

/**
 * Get a value from cache
 * @param store Store to access
 * @param key Lookup key
 * @returns Stored type
 */
export function cget<T>(store: Map<string, ExpiringValue<T>>, key: string): T | undefined {
    const val = store.get(key)
    if (!val) return undefined
    if(val.expires < (Date.now() / 1000)) {
        store.delete(key)
        return undefined
    }
    return val.value
}

/**
 * Store a value in cache
 * @param store Store to access
 * @param key Lookup key
 * @param value Value to store
 * @param ttl Time to live in seconds
 */
export function cset<T>(store: Map<string, ExpiringValue<T>>, key: string, value: T, ttl: number) {
    store.set(key, {
        expires: (Date.now() / 1000) + ttl,
        value
    })
}

/**
 * Delete a value in cache
 * @param store Store to access
 * @param key Lookup key
 */
export function cdel<T>(store: Map<string, ExpiringValue<T>>, key: string) {
    store.delete(key)
}

C

chocolatkey•9/24/24, 8:28 AM

(continued from previous message) implementation:

const thingCache = new Map<string, ExpiringValue<ThingType>>() // Global scope

async function something(id: string) {
    let thing = cget(thingCache, id);
    if(!thing) {
        // Try to get thing from DC cache
        const cacheKey = `things/${id}`
        const dcache = caches.default
        const cachedClient = await dcache.match(`${MY_KV_NAMESPACE}/${cacheKey}`)
        if(cachedClient) {
            thing = await cachedClient.json()
        } else {
            // Finally, try getting it from the database
            thing = await queryTheDatabase();
            if(!thing) return null; // or whatever

            // Place it in the DC cache
            ctx.waitUntil(dcache.put(`${MY_CACHE_NAMESPACE}/${cacheKey}`, new Response(JSON.stringify(thing), {
                status: 200,
                headers: {
                    'cache-control': 'public, max-age=3600' // 1 hour
                }
            })))
        }

        // Place it in the in-memory cache
        cset(thingCache, id, thing, 3600) // 1 hour
    }
    
    return thing;
}

const thingCache = new Map<string, ExpiringValue<ThingType>>() // Global scope

async function something(id: string) {
    let thing = cget(thingCache, id);
    if(!thing) {
        // Try to get thing from DC cache
        const cacheKey = `things/${id}`
        const dcache = caches.default
        const cachedClient = await dcache.match(`${MY_KV_NAMESPACE}/${cacheKey}`)
        if(cachedClient) {
            thing = await cachedClient.json()
        } else {
            // Finally, try getting it from the database
            thing = await queryTheDatabase();
            if(!thing) return null; // or whatever

            // Place it in the DC cache
            ctx.waitUntil(dcache.put(`${MY_CACHE_NAMESPACE}/${cacheKey}`, new Response(JSON.stringify(thing), {
                status: 200,
                headers: {
                    'cache-control': 'public, max-age=3600' // 1 hour
                }
            })))
        }

        // Place it in the in-memory cache
        cset(thingCache, id, thing, 3600) // 1 hour
    }
    
    return thing;
}

const thingCache = new Map<string, ExpiringValue<ThingType>>() // Global scope

async function something(id: string) {
    let thing = cget(thingCache, id);
    if(!thing) {
        // Try to get thing from DC cache
        const cacheKey = `things/${id}`
        const dcache = caches.default
        const cachedClient = await dcache.match(`${MY_KV_NAMESPACE}/${cacheKey}`)
        if(cachedClient) {
            thing = await cachedClient.json()
        } else {
            // Finally, try getting it from the database
            thing = await queryTheDatabase();
            if(!thing) return null; // or whatever

            // Place it in the DC cache
            ctx.waitUntil(dcache.put(`${MY_CACHE_NAMESPACE}/${cacheKey}`, new Response(JSON.stringify(thing), {
                status: 200,
                headers: {
                    'cache-control': 'public, max-age=3600' // 1 hour
                }
            })))
        }

        // Place it in the in-memory cache
        cset(thingCache, id, thing, 3600) // 1 hour
    }
    
    return thing;
}

const thingCache = new Map<string, ExpiringValue<ThingType>>() // Global scope

async function something(id: string) {
    let thing = cget(thingCache, id);
    if(!thing) {
        // Try to get thing from DC cache
        const cacheKey = `things/${id}`
        const dcache = caches.default
        const cachedClient = await dcache.match(`${MY_KV_NAMESPACE}/${cacheKey}`)
        if(cachedClient) {
            thing = await cachedClient.json()
        } else {
            // Finally, try getting it from the database
            thing = await queryTheDatabase();
            if(!thing) return null; // or whatever

            // Place it in the DC cache
            ctx.waitUntil(dcache.put(`${MY_CACHE_NAMESPACE}/${cacheKey}`, new Response(JSON.stringify(thing), {
                status: 200,
                headers: {
                    'cache-control': 'public, max-age=3600' // 1 hour
                }
            })))
        }

        // Place it in the in-memory cache
        cset(thingCache, id, thing, 3600) // 1 hour
    }
    
    return thing;
}

YYash Bindal (yB)Hi Is there any way possible to use ipv4 to hit external APi instead of Ipv6

Y

Yash Bindal (yB)•9/24/24, 8:34 AM

#IPv6 -> IPv4

0

0x146231489231923•9/24/24, 3:47 PM

what web framework you all use in workers??

A

AkuEye•9/24/24, 4:23 PM

hi

A

AkuEye•9/24/24, 4:23 PM

I am trying to update the code in one of my Cloudflare Workers, but the deploy/save button is not working. The button is not giving any option to do anything, due to which I haven't been able to update the code for the past 3 days. Please fix this or suggest a solution.

AAkuEye I am trying to update the code in one of my Cloudflare Workers, but the deploy/s...

H

Hard@Work•9/24/24, 4:23 PM

Try saving the file?

H

Hard@Work•9/24/24, 4:24 PM

CTRL+S

00x146231489231923 what web framework you all use in workers??

C

chocolatkey•9/24/24, 4:44 PM

Hono

K

kingmesal•9/24/24, 5:25 PM

Regarding the https://developers.cloudflare.com/workers/runtime-apis/bindings/version-metadata/

I just want to make sure I'm not missing something and that what I'm seeing is intentional... when running

wrangler dev --remote

wrangler dev --remote

wrangler dev --remote

wrangler dev --remote the

id

id

and

tag

tag

tag

tag are empty and

timestamp

timestamp

timestamp

timestamp is garbage:

{
  "id": "",
  "tag": "",
  "timestamp": "0001-01-01T00:00:00Z"
}

{
  "id": "",
  "tag": "",
  "timestamp": "0001-01-01T00:00:00Z"
}

{
  "id": "",
  "tag": "",
  "timestamp": "0001-01-01T00:00:00Z"
}

{
  "id": "",
  "tag": "",
  "timestamp": "0001-01-01T00:00:00Z"
}

Cchocolatkey Hono

0

0x146231489231923•9/24/24, 5:26 PM

same

0

0x146231489231923•9/24/24, 5:26 PM

anymore other options?

AAkuEye I am trying to update the code in one of my Cloudflare Workers, but the deploy/s...

T

texan•9/24/24, 8:27 PM

If you don't have any changes to your script, it won't allow you to save/deploy. The dot in the top corner of that

worker.js

worker.js

worker.js

worker.js tab shows you have unsaved changes. Control+s should re-enable that button for you

K

kchro3•9/24/24, 8:42 PM

i started seeing errors when running wrangler dev --remote like this:

text: 'Uncaught Error: No such module "node:events".\n' +

Is this related to https://developers.cloudflare.com/workers/runtime-apis/nodejs/#get-started where it says that

Starting on September 23rd, 2024, when your compatibility date is on or after 2024-09-23, the nodejs_compat compatibility flag will enable the exact same behavior as nodejs_compat_v2.

Starting on September 23rd, 2024, when your compatibility date is on or after 2024-09-23, the nodejs_compat compatibility flag will enable the exact same behavior as nodejs_compat_v2.

Starting on September 23rd, 2024, when your compatibility date is on or after 2024-09-23, the nodejs_compat compatibility flag will enable the exact same behavior as nodejs_compat_v2.

Starting on September 23rd, 2024, when your compatibility date is on or after 2024-09-23, the nodejs_compat compatibility flag will enable the exact same behavior as nodejs_compat_v2.

I only started seeing this issue today and nothing materially changed from my set up yesterday

Cloudflare Docs

Node.js compatibility | Cloudflare Workers docs

Node.js APIs available in Cloudflare Workers

R

root@alien:~#•9/24/24, 10:48 PM

Why do I get this error after selecting the smart option in cloudflare workers? "placement is currently unsupported when using assets"

Rroot@alien:~#Why do I get this error after selecting the smart option in cloudflare workers? ...

T

texan•9/24/24, 11:09 PM

Thanks for letting us know! We're working on fixing this!

Edit: fixed!

CCorsix👾to have several service bindings to other workers in one worker, what's the corr...

R

Radoš•9/24/24, 11:14 PM

you can also do it like this

[[services]]
binding = "AUTH"
service = "myproject-auth"
entrypoint = "MyProjecAuthEntrypoint"

[[env.production.services]]
binding = "AUTH"
service = "myproject-auth"
entrypoint = "MyProjecAuthEntrypoint"

[[services]]
binding = "AUTH"
service = "myproject-auth"
entrypoint = "MyProjecAuthEntrypoint"

[[env.production.services]]
binding = "AUTH"
service = "myproject-auth"
entrypoint = "MyProjecAuthEntrypoint"

[[services]]
binding = "AUTH"
service = "myproject-auth"
entrypoint = "MyProjecAuthEntrypoint"

[[env.production.services]]
binding = "AUTH"
service = "myproject-auth"
entrypoint = "MyProjecAuthEntrypoint"

[[services]]
binding = "AUTH"
service = "myproject-auth"
entrypoint = "MyProjecAuthEntrypoint"

[[env.production.services]]
binding = "AUTH"
service = "myproject-auth"
entrypoint = "MyProjecAuthEntrypoint"

Rroot@alien:~#Why do I get this error after selecting the smart option in cloudflare workers? ...

W

Walshy•9/24/24, 11:40 PM

This is fixed, sorry for the issue!

S

SpiraTech•9/25/24, 12:33 AM

just a note for anyone thinking of staying with mailchannels via contacting their sales team, you need credit card info on record to keep using it free so I'm no longer interested. I've instead migrated to resend and it's working better than ever!

R

Radoš•9/25/24, 12:34 AM

@SpiraTech just create a worker connected to Amazon SES and you are set for any project and it costs nothing.

R

Radoš•9/25/24, 12:35 AM

There is even a repo on GitHub.

RRadoš @SpiraTech just create a worker connected to Amazon SES and you are set for any ...

S

SpiraTech•9/25/24, 12:35 AM

that is probably a great idea, I am a bit too dumb, and I only need a few emails a month so I kept it simple and integrated into my pages worker - well with help from ChatGPT lol

Thanks for the info though I'll check that out if I need to use anything else with more emails in the future! thanks

R

Robin Genz•9/25/24, 6:10 AM

Hey

I'm using the Rate Limiting API to define rate limits in my worker. I could not find any information on how long a rate limiting remains active once it takes effect. Is there any information on this?

Cloudflare Docs

Rate Limiting | Cloudflare Workers docs

Define rate limits and interact with them directly from your Cloudflare Worker

Hello everyone, I'm looking to implement a caching strategy for my Cloudflare Worker to **optimize t

Similar Threads

Similar Threads

Similar Threads