Node Ed 25519 is in , if that's what you mean

Yes, but looks at this: https://developers.cloudflare.com/workers/platform/changelog/#2023-04-28 actually there's more

I don't have enough web crypto knowledge for that to mean much to me unfortunately

If you think a clarification could be made to the docs, the best place to ask is an issue @ https://github.com/cloudflare/cloudflare-docs

OK thanks

added it as an issue

Answering my own question: when doing

env.worker_binding_variable.fetch()

you pass in a

new Request()

where you create a

new URL(request.url)

where request.url is the url from the request object from

export default app...

but change the pathname to whatever you want.

still persists even with the new 3.0.0 version that came out this week. Anyone have any idea? Also created the issue https://github.com/cloudflare/workers-sdk/issues/3300

This is a known issue here: https://github.com/cloudflare/workers-sdk/issues/3264

oh ok. I'll reference this and close my duplicate issue then

if im using ittyrouter in a worker, can you call a route from within another route in a worker?

Service bindings. Using itty-router isn't really relevant

I would like to ask that what is the average wait time for wait list of the Browser Rendering API as I want to use it badly.

thnx buddy 🙂

Have a link? Care to elaborate a bit ?

So service bindings you gotta call another worker from another? It's not like one worker can have a bunch of functions / routes and call them from eachothrr

yes that is what a service binding is for

of course you could share functions using packages or something

For the websocket protection there are no numbers just small etc. Is there any guidance on what to expect in terms of numbers? I dont want to get hit by facts later on 😮

GAHHHHHH I spent so much time working around this, didn't know

NODE-ED25519

existed..........

>_>

that's frustrating.

i'm looking at making a simple page / site that takes aggregated data scraped from web pages and displays that info i wanted to try out CF workers / pages to do it. does this make sense: - a worker that runs daily and scrapes the pages. (can i do a fanout technique with workers?) -- persist that data in some CF datastore - a pages setup with next.js that just pull the latest from the datastore if so, is there a recommended way to keep this all in one repository? is it easier to just have multiple repos and use wrangler for the worker and

@cloudflare/next-on-pages

for the app?

Hello, I need to speak with someone from the Workers' team. Our website is down, and I'm receiving an error message

Worker exceeded resource limits 1102

. The dashboard doesn't provide a clear explanation of the error, and we haven't received any messages regarding this issue. Our production site is entirely down, and there is no billing problem or soft limit that we need to configure. I'm curious if this is a Cloudflare issue, as we are currently experiencing technical problems. I require immediate assistance, but the support system says it could take up to three days to address our issue. Could someone provide me with more details on how to modify the limit, or resolve this problem? At present, our root pages on https://wope.pages.dev are functioning, while the reverse proxy on our domain, https://wope.com, is down. Any comments?

Are you on a paid Workers plan?

Yes, paid Workers plan for 2+ years. I have meticulously checked every detail, and it appears that my website is completely down. I discovered this issue by accident since I received no notifications via message or email. It seems like a rare bug that happened in Cloudflare without any forewarning. Unfortunately, the only solution to prevent this in the future is to disable Cloudflare for my root domain's CNAME record, which will disable the reverse proxy. This solution will only temporarily resolve the problem :/

Seems to load fine for me in both places

Maybe there is an edge case somewhere in your code that causes something to overrun the limits?

it loads fine for me too