why does it just time out a sub request if SSE events get sent for 100 seconds?
why does it just time out a sub request if SSE events get sent for 100 seconds?
CCloudflare with supabase integration is broken, I get a 400 error when I try oauth
2can someone assist me with the edge runtime do I specify it in everypage on nextjs
2on existing projects
RCan someone please help me on this
No one replied till now, i am stuck
workers-and-pages-helpWorker route not working
No one replied till now, i am stuck
workers-and-pages-helpWorker route not working
Suhm is it normal that .dev.vars are inside your server bundle? :AL_yEthinkHmm:
HWhat framework is that?
Swell happened to me on svelte worker assets but same happens with https://github.com/cloudflare/agents-starter
if you add a .dev.vars in the root
if you add a .dev.vars in the root
GitHub
A starter kit for building ai agents on Cloudflare - cloudflare/agents-starter
Kany thoughts on sub request just closign networ connection lost after 100 seconds? it doesn't make sense to time this out for a backend request thats making a long running request
TIs there any way I to get custom domains without a zone on cloudflare working on Workers w/ Static Assets? I've only noticed just now and it's too late to go back - impossible to get the domain on Cloudflare.
Ware worker "frameworks" replacing pages?
CThe Cloudflare wide Proxy Read Timeout is 100 seconds https://developers.cloudflare.com/fundamentals/reference/connection-limits/, if your backend is that slow you'll need to speed it up, have it use a job style where it returns that it's running and to poll for status, etc. For SSE specifically, I haven't tried it but there's a few posts mentioning it kind of works and that 524's only trigger if nothing is sent within 100s
CNot if you have no zones at all. If you have at least one, even just a throwaway/random ones, can use CF For SaaS: https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin/ and have your real custom domain CNAME to it, which then would run your worker. More meant for full SaaS cases though. It's the same thing Pages uses under the hood
CFrameworks is just their list of guides in the docs, "Workers Static Assets" is the underlying replacement, allowing Workers to support static assets just like Pages. CF has said before they plan on offering more migration steps in the future to Workers Static Assets from Pages, but eventually they will converge
TUnable to preview your Worker
Mif a worker connects to a cloudflare tunnel endpoint, and there's a WAF rule to block any non-worker traffic, eg.
how much latency should both the WAF rule & cloudflare tunnel be adding?
how much latency should both the WAF rule & cloudflare tunnel be adding?
Cwaf should be too small to measure, tunnel is more complex. I'd make sure you're connecting to a nearby PoP (
example.com/cdn-cgi/trace
Mif the worker memory limit is 128mb, wouldn't I run into that if I use the kv store .list() operation and retrieve 1280 keyvalue items with a size of 100kb? I mean those string values get loaded into memory if I .get() them all one by one in a for loop? I guess the GC would be able to start running if that's how it works in a loop with a memory limit set.
Tthanks so much! this worked well
L
JCloudflare Team: Does this https://discord.com/channels/595317990191398933/1040420029080018945/1354117859671805964 announcement mean that
ctx.waitUntil()
ZChaps when connecting github, I can only see repositories created by the account that was connected. It doesn't show repos shared with me. Is there anyway repos shared with me can be used?
Wno, waitUntil hsa not changed
JCool cool cool. Any chance they might happen in the near future? 
Min this worker code im measuring time to hit origin. it starts off ~350 and then after a few refreshes, becomes a mixture of ~350 and ~100
is this TCP or HTTP keepalive at play? are there any viewable stats, or any ways that I can get the ~100 to occur more frequently?
is this TCP or HTTP keepalive at play? are there any viewable stats, or any ways that I can get the ~100 to occur more frequently?
DI read something somewhere (a while ago) about workers being favored in the future in place of pages. Did I read that wrong? Can't find anything on pages getting deprecated or something.
VHey. Pages is still supported but longer term we want to get to a point where every new application can be built on Workers
VIf there are gaps preventing you from using Workers today (and instead choosing Pages), we’d love to hear about that
TIs it possible to setup a subdomain for cloudflare workers without either
If not, is it planned in order to have feature parity between cloudflare workers & pages?
- Setup the apex domain within cloudflare
- Pay 250 dollar a month to setup a subdomain zone
If not, is it planned in order to have feature parity between cloudflare workers & pages?
HUse SSL for SaaS yourself, like Pages does?
TBut then I would need to create a zone within cloudflare with a domain, or I might have missed something?
HYeah, you would need one zone at minimum on Cloudflare
JHi there! I'm trying to build a worker that does realtime audio "splicing" from component mp3s. Essentially based on an audio file layout, grab the files from r2, remove header info and splice the mp3 audio data together and stream.
I've succeeded in building this. But now I'm running into a problem that seems maybe unsolvable: clients expect to be able to issue range requests in a header asking for specific bytes in the audio (I'd like to listen starting at 10:00 in...).
What I'd ideally like is that an initial request will be cached entirely, and then the cdn would take over to respond to the range request with a proper 206 response and the bits. There doesn't seem to be a way to do this.
I've succeeded in building this. But now I'm running into a problem that seems maybe unsolvable: clients expect to be able to issue range requests in a header asking for specific bytes in the audio (I'd like to listen starting at 10:00 in...).
What I'd ideally like is that an initial request will be cached entirely, and then the cdn would take over to respond to the range request with a proper 206 response and the bits. There doesn't seem to be a way to do this.
- If I respond with a 206 from the worker, it can't be cached
- If I respond with a 200 with the whole file, the client doesn't get what it asked for
HYou would need to implement this cache slicing logic in your Worker. Worker responses can’t be cached, so requests will always be billed. Note however that they can interact with the Cache API as part of their handling of a request
JIs there no way to rely on range request handling from standard cloudflare cdn? Like front a worker with the standard cdn?
JThe other huge gotcha here is that anything besides directly streaming from r2 out to the client will quickly surpass the memory limits of a worker. Audio is large, but the streaming solution built works well as it just streams it through without holding much in memory.
Any caching of the whole thing (or writing out to r2 for a "tempfile") is going to need it loaded in memory, which cannot work.
Any caching of the whole thing (or writing out to r2 for a "tempfile") is going to need it loaded in memory, which cannot work.
HWorkers are a layer of the CDN on top of the cache. They can interact with it, but responses from a Worker will not be cached themselves
HYou don’t need to buffer the whole thing in memory, you can stream directly from R2 into the Cache
Dthanks a lot 
No shortcomings, just curiosity because this recommendations are not really easily findable
No shortcomings, just curiosity because this recommendations are not really easily findable
MRIP i just wasted an entire day going down the websockets rabbit hole only to realise discord has a cloudflare ban so i can't use workers with DO for their gateway api :(:(
Mthey just 401 when a new connection attempt originates from a worker ip
Mand from what ive read the only way around this is with Aegis but that's enterprise only
Mproxy policies would be cool on a per-worker basis
Mim fine hosting a proxy on my own server just to get around the discord cloudflare ban :\
Malthough that will add even more layers of complexity and latency for the traffic so not optimal
