any idea if this will work? this.state.storage.delete(this.state.id.toString()); (from within a durable object)

It would delete something in DO storage that matches the current ID of the DO, if that is what you mean?

yes

thanks

It won’t delete the DO itself though, if that is what you mean

i mean the storage (i think)

It will only delete a single item

You're currently only listening on

/

so anything else will just receive an error page

Hi, is SIMD available on workers through WASM?

I probably shouldn't generate RSA keys in Cloudflare Worker right?

I should generate it on clients device and then send it to the worker

in most cases you'd probably want to keep the keys in the same place they were generated

not sure why you'd want the client and server to both know the keys

Yeah when I tested this SIMD was available.

If worker sites are deprecated, am I "stuck" on worker sites as long as I need

/api

requests to passthrough and hit an origin server? 99% requests are static assets so cloudflare pages look enticing

You can use Functions with Pages to accomplish the same thing 😀

A Function in

/api/[[path]].ts

for example

What is the syntax for passing through to the origin server? A naked

return;

without a response that works in Worker sites doesn't work in functions (at least locally)

You’d need to

fetch

the api manually. So something like

return fetch(url);

Where

url

is something you construct from the path +

api.example.com

for example

Ah, so you're suggesting moving api requests to another domain?

You'd have to because Pages custom domains have Pages as the origin

You can't overlay it as a Worker route

Gotcha, and what is the best way to ensure that only requests from this pages function can hit the origin server?

Like just throw up some basic auth? Or something else?

what is the origin server? if it's another worker you can add a service binding which won't even go over the internet and doesn't need any auth

It's a service on a VPS that cloudflare worker sites currently passes requests to if an

/api

route is detected. It's behind traefik, so adding a custom domain + basic auth shouldn't be too hard. Eventually I'd like to move all the api routes into cloudflare pages functions, but I'd like to transition one endpoint at a time

It seems like parsing a 1MB json blob exceeds the 50ms compute limit. There isn't a faster or cloudflare worker specific way of parsing JSON responses that is faster right?

i'm sure i've parsed JSON way bigger than 1MB before 🤔 can you share an example?