Yeah that request is getting blocked because of the host header being "127.0.0.1:8787" the host head
Yeah that request is getting blocked because of the host header being "127.0.0.1:8787" the host header should be whatever the domain is.
Fok, it work on workers.dev, but in my domain, it return 405
Fit's because the pages?
Fjust a router error, it can work now, thank you
CHello everyone, I am integrating the workerAI with Langchain4j to bring visibility to this great asset https://github.com/clun/langchain4j/tree/provider-workerai. Most of the features are their. I have question regarding the 
text-to_Image 
Phey im getting this error with wrangler
Pit worked fine like 5 minutes ago
Panyone knows what might be going on? There`s nothing on cloudflares status page
CGitHub
Support for Worker AI
CloudFlare opened a Beta of a new service Called WorkerAI
https://developers.cloudflare.com/workers-ai/
They do provide a REST API for different operations.
Text Generation
T...
CloudFlare opened a Beta of a new service Called WorkerAI
https://developers.cloudflare.com/workers-ai/
They do provide a REST API for different operations.
Text Generation
T...
GHi all. Say I have a zone called
Any ideas/thoughts?
Correction: it seems to break whenever I remove the workers route from the old
foo.bar.com and a workers route for *.foo.bar.com/* that goes to my worker, plus a proxied DNS record for *.foo.bar.com. All that works fine. Then we decide to create a zone for bar.com and migrate off foo.bar.com into this zone. Added the same proxied DNS record to this bar.com zone and the same workers route. Issue we're seeing is that the requests seem to go straight to the origin server but they don't seem to be hitting the worker at all.Any ideas/thoughts?
Correction: it seems to break whenever I remove the workers route from the old
foo.bar.com zone. I want the new bar.com to process these requests, not the old zone 
FWhat is the CPU limit accounting when using a bound worker with the new billing system? Does the worker called with fetch get counted as part of the caller's CPU usage, or does it get its own limit?
FIf it were called via the network, it would get its own limit and the caller time would pause while awaiting for the result of the fetch, right? Is it similar for a bound worker call?
LAre there any plans to reduce the cold start latency of workers? Its quite bad right now
LDo you have any idea how much this can help/what target cold start time is? Articles like this even claim there is zero cold start, but in practice I see anywhere between 50-500ms
LSpot checking response times from different locations, comparing first to subsequent requests. I had a lengthy convo with a support engineer a while ago but he wasn't able to figure out why with worker was impacted in this way, but without wasn't, so I just assume its something weird in the worker runtime
HBasically, below 1 MiB you use Quicksilver, the DB that supports Zero Cold Starts. Above 1 MiB, you run from Cold Storage, which does not
LGot it, do you have any sense of the latency distribution for running off of quicksilver vs cold storage?
HIt should just be an instant drop off, like you are observing
HIf you get it below the limit, then it should just be 0(minus TLS start/other stuff)
LWhen I deploy this is what I see, is the limit based on compressed or uncompressed? Seems its already under but maybe something is still sending it to cold storage since its close?
HCompressed. Just to be sure, are you paying for Workers atm?
Lyeah, enterprise and unbound
HWeird…
HYeah, not sure what else could be causing that
CThe other thing is about how your worker runs. If you use a route that specifies a specific path the magical cold start stuff can't work
Chttps://blog.cloudflare.com/eliminating-cold-starts-with-cloudflare-workers/
For now, this is only available for Workers that are deployed to a “root” hostname like “example.com” and not specific paths like “example.com/path/to/something.” We plan to introduce more optimizations in the future that can preload specific paths.Edit: If it's more then ~50ms then it sounds more like global scope then cold start not working though, tcp connect isn't that long
Chey, i'm creating a minimal email worker that's making a post request to a slack webhook. all good and working. the problem is i'm missing email body. i was looking for it on but is not there
UGitHub
An example of a worker that parses an email. Contribute to edevil/email_worker_parser development by creating an account on GitHub.
Caha, i see ty @Unsmart | Tech debt
Aevery time I deploy my worker the kv bindings is removed from my worker. I tried:
Cdoes email workers are supported in wrangler?
INot sure if it would be a matter of getting credit, but more that you can't run your own models on Workers AI yet.
LI tested with a simple proxy and same issue
LDoes this apply if I have it at root but add a query string?
Also what do you mean by global scope being an issue?
Also what do you mean by global scope being an issue?
MCan the automatic running of cloudflare worker code while I'm typing be turned off? I can't work like this when I get basic auth popups every split second and I dont see the advantage of my worker constantly running on each keypress when I can use the Send button anytime I need to run
HYou may be able to disable it in the settings, but otherwise, you can develop locally and push
MI dont see an option for this but I think I may have a workaround.. I have to cause a syntax error and then it doesnt run constantly
Mnevermind it still runs
BHi, I am having problem with r2 audio/video file uploaded via presigned URL (PutObjectCommand). It was being uploaded but when we are going to use it via signedUrl(GetObjectCommand) for transcription, file cannot be read for transcription. The get presigned and signed URL are generated through Workers. I tried to download it and played in media player, and still it was unable to play the file. Did I missed something in upload using presigned url ?
but when I upload the file directly in R2, then transcribed the file via signedUrl, the transcription service that we are using are successfully able to transcribed it
but when I upload the file directly in R2, then transcribed the file via signedUrl, the transcription service that we are using are successfully able to transcribed it
ZHey,
I'm currently trying to minimize latency as much as possible. I am currently using Cloudflare hyperdrive with my postgres db + a cloudflare kv cache for my entries, but I am still getting around 100ms latency. Is there any way to reduce this further? I am just running a simple select query and my return size is about 4KB. I attached an image of what my route looks like, and an image of what the respective latency for each operation is. I also attached an image for my db middleware to allow me to use my db in ever call. I know this is not very effective, but almost all my routes use a DB call anyway. Or is there any way to reuse an existing connection?
I'm currently trying to minimize latency as much as possible. I am currently using Cloudflare hyperdrive with my postgres db + a cloudflare kv cache for my entries, but I am still getting around 100ms latency. Is there any way to reduce this further? I am just running a simple select query and my return size is about 4KB. I attached an image of what my route looks like, and an image of what the respective latency for each operation is. I also attached an image for my db middleware to allow me to use my db in ever call. I know this is not very effective, but almost all my routes use a DB call anyway. Or is there any way to reuse an existing connection?
UI would remove the cache and remove the 2nd db connection that doesnt use hyperdrive and it should be faster 
Uand if theres some reason you really dont want to use hyperdrive for a specific route I would make it where you return only the hyperdrive connection or only the direct connection instead of opening both
ZWhy remove the cache? It seems to be much faster. Just trying to understand
Uhyperdrive already adds a cache so that would just double cache now
ZTrue, but for some reason the Hyperdrive cache is way slower. It adds about 80ms of latency
ZWould cloudflare D1 be better for my use case? I just want the lowest latency possible
ID1 would be lower latency in the location where it's created, but it's also SQLite (not Postgres) so anything Postgres specific won't work with D1.
DI am using photon-rs using WebAssembly, and the worker throws
Error 1102: Workers Resources Limit, I think it's due to CPU time limit. How can I check the cpu time taken by a fetch handler?
EHi, everyone. Sorry for bothering you, but I need your help
I hosted a static website using Cloudflare workers to optimize the performance
how can I increase the page speed? what should I do, like configuring or anything else?
I hosted a static website using Cloudflare workers to optimize the performance
how can I increase the page speed? what should I do, like configuring or anything else?
