hmm I guess we don't badly need it on anything except path now that I think about it more.

since for the crazy header based routing (thanks AWS....), we only need to do a round-trip to a backend once in most cases.

I'm sure it could end up more intelligent than that with a lot of work - but I feel like pathname is a slightly more reasonable demand 😅

How do I prevent my custom route from re-routing back to the worker.dev route?

Could you elaborate?

Would you be willing to look at my question in the wokers-help channel? It might be a little much for this channel

This is the link if you have time: https://discord.com/channels/595317990191398933/1107861271447085056

Ah yes, I didn't see it

I just read that Date.now() is disabled in workers. I had to do some reading to understand how that's a security concern, but that leaves me wondering if there's an alternate timing method available for measuring response times for D1 queries? I haven't attempted this yet, but I've been brainstorming on some experiments for evaluating D1 performance.

Date.now is not disabled its just not 100% accurate it can be off by ~2 seconds

and in the same request running Date.now() twice to time something should be good enough

You can just measure the Worker's overall response time too.

@sathoro awww the database integration doesn't handle rotating secrets :/ https://developers.cloudflare.com/workers/learning/integrations/databases/#what-happens-to-the-database-integration-if-i-rotate-my-database-credentials

great clarification, thanks

if i serve content from another s3 service but using cloudflare workers and without caching, does that still constitute violation of the new CDN terms? () > Finally, we made it clear that customers can serve video and other large files using the CDN so long as that content is hosted by a Cloudflare service like Stream, Images, or R2.

As long as there is I/O in between. If it is just computation, then it will be frozen

Hi guys, is it possible to get miniflare/workerd to respect

--local-upstream

when running

wrangler dev --experimental-local

?

Alternatively, how do I get the

--host

option to work with my domain provided by dynu.net (essentially dyndns)?

This isn't very clear instructions. Do I need to wrangle this down locally then run this? It never says how or where to do this and I got thrown off because there's seemingly no direction on where to put it (the rest of the guide is on the dashboard so it's only logical this is also there, but I couldn't find it)

yes. you would run that locally

you need the Supabase library to use Supabase

yeah I figured, maybe add an intermediary step to say "clone the site locally with wrangler" or something, thank you! love to see the supabase integration

Not cloudflare but I believe so.

That one IMO still is not clear in the TOS but from what the CEO has said on Hacker News before... yes you can:

thanks for finding this

And fwiw that also did have cache turned on and he said it wasnt a problem so 🤷

Any idea what I'm doing wrong? https://miniflare.dev/testing/vitest#waiting-for-waituntiled-promises

oh maybe this... https://github.com/cloudflare/miniflare/blob/master/docs/CHANGELOG.md#features

ah fudge, what's up with this?

[mf:err] POST /api/aws-compatible: TypeError: Failed to parse URL from [object Object]
    at new Request (/Users/dave/Work/yourcrowd-api/node_modules/undici/lib/fetch/request.js:81:15)
    at new Request (/Users/dave/Work/yourcrowd-api/node_modules/miniflare/node_modules/@miniflare/core/src/standards/http.ts:466:13)
    at Miniflare.dispatchFetch (/Users/dave/Work/yourcrowd-api/node_modules/miniflare/node_modules/@miniflare/core/src/index.ts:1077:51)
    at Server.<anonymous> (/Users/dave/Work/yourcrowd-api/node_modules/@miniflare/http-server/src/index.ts:291:20)

fixed by switching to

--experimental-local