I believe it's `request.cf.botManagement.verifiedBot`
I believe it's
request.cf.botManagement.verifiedBot
ADoes
I added
I'm sure my tail worker is called
wrangler.toml in the code editor from the dashboard work?I added
tail_consumers = [{service = "tail"}] in the file but it didn't work.I'm sure my tail worker is called
tail and the worker has tail(event) function.
ITail workers are quite hard to debug, you can try the dashboard logs and potentially create an endpoint in that tail worker that mocks some of the tail events to test if your worker is doing what you expect to do.
IQuestion in regards to service bindings, reading environment variables and latencies. I've a worker called Edge Config that exposes 2 RPC functions,
It's a Pages -> Workers service binding, both have smart placement turned off. Is this latency normal, how can I further reduce this? Any other recommendations to have dynamic config with close to 0 latency for reads?
setSecret and getSecret. setSecret updates the secrets of itself using the Cloudflare REST API. getSecret returns the environment secret binding. I expected it to be close to 0 latency for doing an RPC call to Edge Config and returning a secret, but it ends up being around 147ms for the RPC call to get an environment variable. The whole reason I have this setup is to have close to 0 read latency to get some dynamic config values.It's a Pages -> Workers service binding, both have smart placement turned off. Is this latency normal, how can I further reduce this? Any other recommendations to have dynamic config with close to 0 latency for reads?
AI added this in the
fetch function to test and it works well, so I think the problem isn’t on the tail functionAWhat is https://internet-measurement.com/ ? It keeps requesting to my worker on different ports like 8443, 8880 and 2086
Nwell you can read maybe 
AHow do I block them?
Cthere's tons of companies and projects which scan the entire web and ip space, not particularly harmful,espec not to a worker which isn't going to be vuln to anything
Cif you want to try to block those, disable your workers.dev for that worker and use Custom Domains/Routes to bind your worker to your domain, and you can use a rule like
not cf.edge.server_port in {80 443} to block all traffic to non-standard portsNwhy 
AMy workers send me a discord message in some cases, it’s a bit annoying to receive messages when I didn’t call them
Nyou will always get some random requests
Sif (request.cf && request.cf.botManagement) {
const verifiedBot = request.cf.botManagement.verifiedBot;
if (verifiedBot) {
return fetch(request);
const verifiedBot = request.cf.botManagement.verifiedBot;
if (verifiedBot) {
return fetch(request);
Sdoes it work like that ??? does it work for busniess plan ???
SIs there a way to rate limit the worker such that requests that are rate limited d onot count towards the request limit?
WSI just checked and I dont find request.cf.botManagement on cloudflare worker , should I get specific bundle from cloudflare to get it
Jhas anyone written a worker based redirect / rewrite / proxy with configuration similar to netlify's _redirects?
JI'm imagining it would also support bound services
Jotherwise I'll try and scrape something together myself..
BHello, i am new, how is add domain and how update file??
Bthere delete main.
B:coffeleark:
Band can use laravel yes?
HWorkers(Unbound isn't really a thing anymore), while not a dedicated "heavy-compute" solution, gives you 30 seconds of CPU Time for HTTP(S) requests
Fhey! in my pages proejct i'd like to add some extra workers. how can i put them into a subdirectory with their own wrangler.toml and deploy?
Fah
-c will do the trick.II managed to bring this down to
"Service bindings are fast. When you use Service Bindings, there is zero overhead or added latency. By default, both Workers run on the same thread of the same Cloudflare server."
And all the RPC call does is read a environment variable. Curious if anyone has any insight into this?
~91ms by setting the edge config worker to smart placement I guess? But the binding latency is still not 10ms< which I expect since service bindings should run on the same thread / isolate right? In the docs it states:"Service bindings are fast. When you use Service Bindings, there is zero overhead or added latency. By default, both Workers run on the same thread of the same Cloudflare server."
And all the RPC call does is read a environment variable. Curious if anyone has any insight into this?
HHow are you testing the speed?
ITime.now before and after the RPC call and log tail that pushes it to a log aggregator (axiom)
HAre you doing any other work before that point?
NI was following the Cloudflare Workers KV quick start guide and ran into an unavoidable error:
✘ [ERROR] Error processing request: TypeError: Cannot read properties of undefined (reading 'put')
I have no idea what this error means, and there aren't any docs or resources available to help.
✘ [ERROR] Error processing request: TypeError: Cannot read properties of undefined (reading 'put')
I have no idea what this error means, and there aren't any docs or resources available to help.
H?channel-crossposting
FPlease do not post your question in multiple channels per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.N
HCan you also share the code you are using to test?
Nexport interface Env {
YOUR_KV_NAMESPACE: KVNamespace;
}
export default {
async fetch(request, env): Promise<Response> {
try {
await env.YOUR_KV_NAMESPACE.put("KEY", "VALUE");
const value = await env.YOUR_KV_NAMESPACE.get("KEY");
if (value === null) {
return new Response("Value not found", { status: 404 });
}
return new Response(value);
} catch (err) {
// In a production application, you could instead choose to retry your KV
// read or fall back to a default code path.
console.error(
return new Response(err, { status: 500 })
}
},
} satisfies ExportedHandler<Env>;
YOUR_KV_NAMESPACE: KVNamespace;
}
export default {
async fetch(request, env): Promise<Response> {
try {
await env.YOUR_KV_NAMESPACE.put("KEY", "VALUE");
const value = await env.YOUR_KV_NAMESPACE.get("KEY");
if (value === null) {
return new Response("Value not found", { status: 404 });
}
return new Response(value);
} catch (err) {
// In a production application, you could instead choose to retry your KV
// read or fall back to a default code path.
console.error(
KV returned error: ${err})return new Response(err, { status: 500 })
}
},
} satisfies ExportedHandler<Env>;
HGood catch
Nit worked
LHi, I want to make websocket server for a game in worker. What does "Max of 30 seconds of CPU time per invocation" or "10 milliseconds of CPU time per invocation" mean? Does my websocket stops if it go over?
NHey @Mike Nomitch | Workers PM regarding your recent message on the announcement channels about containers in the workers platform, we have a very specific use case that is currently being delegated to fly.io which basically consists of the execution of long running tasks in an asynchronous manner, think of it as a job runner that can run a container instance to completion with parameters passed as environment variables.
We basically use it as a way of executing bulk Tasks like post processing on media, AI tasks, report generation, RPAs, puppeteer and other such things where system dependencies are needed.
Our main reason for delegating it to fly.io right now is that they don't impose a time limit so our long running tasks don't get timeouts while still providing quick startup times once the image is cached.
We find that currently no cloud provider provides a complete solution for running asynchronous jobs while just paying for the compute time and providing fast startups (we achieved that with fly.io but it required us to hack around with their platform API and writing our own scheduler) so I think that would add great value to the Cloudflare developer platform.
We basically use it as a way of executing bulk Tasks like post processing on media, AI tasks, report generation, RPAs, puppeteer and other such things where system dependencies are needed.
Our main reason for delegating it to fly.io right now is that they don't impose a time limit so our long running tasks don't get timeouts while still providing quick startup times once the image is cached.
We find that currently no cloud provider provides a complete solution for running asynchronous jobs while just paying for the compute time and providing fast startups (we achieved that with fly.io but it required us to hack around with their platform API and writing our own scheduler) so I think that would add great value to the Cloudflare developer platform.
DDoes anyone know what is the key for package.json conditional exports for wrangler esbuild?
worker, workers or workerd
KIt'll also try
worker then browser if there is no workerd key.