You'd need to wait for Snippets if you want to run a Worker in response to a WAF rule.
You'd need to wait for Snippets if you want to run a Worker in response to a WAF rule.
Mwhat you mean by Snippets , can you explain in more details please
KCloudflare Snippets (alpha) provide a flexible way to customize the behavior of your website or application using short pieces of JavaScript code. Use …
Mits still beta and I dont have access to it , is there any other way ??
KNope, Workers currently are always invoked on a given route.
KWhat are you trying to do, invoke a Worker based on a rule or replicate rule logic in a Worker?
Minvoke a Worker based on a WAF rule , (( so I just want the Worker to be triggered only when specific CUSTOM waf rule triggered )) currently its triggered on all (( skip )) waf rules
KYeah, you can only do that with Snippets when they become available.
UWhy do you want to trigger a worker by a WAF rule though? 
Mvpn detection system , currently there are a lot of good bots being detected as vpn , and they got blocked by the worker
Mand I want the worker to not work on (( custom waf rule == known bots ))
KJust to make sure, you are aware that Known Bots means it's a good bot.
Myes I know
KGotcha
Mcurrently my vpn detection system see that most of the good bots as proxy and vpn and they are blocking them
Mso I want to bypass worker if it hit the known bots rule
Mwow ! thats great , by the way what you mean by (( iirc that' the name ))
KThere's
verifiedBotCategory which will be "" if it's not a known bot, otherwise containing the category of the bot.Mwow thank you !
Mif (request.cf.verifiedBot) {
// Logic for handling verified bots
// You can choose to bypass certain operations or handle them differently
return fetch(request);
}so it should be something like that , verified and known bots will hit this
// Logic for handling verified bots
// You can choose to bypass certain operations or handle them differently
return fetch(request);
}so it should be something like that , verified and known bots will hit this
SOn the "Overview" page for Workers & Pages, I can see the sum of all my requests and CPU time, etc.
It is not possible, however, to get a breakdown on which Pages projects are using how much unless I click into every project, go to function metrics, and then adjust the timeframe to something other than "last 24 hours"
Is there any way I can view a usage / billing breakdown, even via the API?
It is not possible, however, to get a breakdown on which Pages projects are using how much unless I click into every project, go to function metrics, and then adjust the timeframe to something other than "last 24 hours"
Is there any way I can view a usage / billing breakdown, even via the API?
DIs there an easy way to throttling my subrequests globally?
DI'm using a stupid Azure service that 429's me a lot.
JQueues maybe? You could limit consumer concurrency to a low number
JAssuming you can batch them up into jobs or similar
JI don’t know of any easy way other than that, outside of using durable objects to track and throttle
Dah yep, sounds like queues would be the "easiest" using 
max_concurrency. Dmight be too much of a hassle for this project to rewrite it with queues in mind, but probably should refactor it to do that eventually
CYou can use the GraphQL API to get the metrics https://developers.cloudflare.com/analytics/graphql-api/tutorials/querying-workers-metrics/
<y'know I gotta say,
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:The whole stack trace below just points to the miniflare lib, not my own code, so I have no idea what ever causes this, I have to fumble in the dark like a caveman using ECMAScript 1 in 1998
JCommon issue right now, sorry! There’s a fix up at https://github.com/cloudflare/workers-sdk/pull/4719 which should hopefully land soon
GitHub
Fixes #4715.
What this PR solves / how to test:
Previously, if in a wrangler dev session you called console.log() and threw an unhandled error you'd see an error like [ERR_ASSERTION]: The expre...
What this PR solves / how to test:
Previously, if in a wrangler dev session you called console.log() and threw an unhandled error you'd see an error like [ERR_ASSERTION]: The expre...
<I have an older version of the worker lib, so does it come from elsewhere?
<Can't wait for this to be fixed either way this is really aggravating and I don't like the feeling of frustration that comes with it
JHow old? This was introduced a couple months ago I think
<3.0.0 I think
JYou can grab the pre-release in that PR if you want to give it a try
<I rolled back after trying to update from a warning lol
<I'll try the PR, that might at least hold me off until the fix
J3.0.0 is very very old, I would definitely not recommend a version that old
<Tru dat
<Actual errors 
SThank you, I'll take a look at this
FHey, is cloudflareworkers.com an official Cloudflare domain/service?
CBest place for an official answer would be an account ticket with support. I don’t think there’s anything wrong with doing it given you have permission
Jfrom the early days, but yes - here is a release notes that references it: https://community.cloudflare.com/t/2018-11-29-workers-runtime-release-notes/47396
CSI gave this a shot. It's a bit complicated but from what I can see, the workers endpoint you referenced is specifically for workers. I found an endpoint for "pages", but i'm unable to get the name of the pages project in the results. I instead get back a randomized
Any insight on this? Are there any other solutions? I find it bizarre that I can't get a breakdown of usage per project (without going into 50+ project dashboards manually). Hopefully Cloudflare is working on some improvements to that.
scriptName e.g. pages-worker--123456-production for each invocation.Any insight on this? Are there any other solutions? I find it bizarre that I can't get a breakdown of usage per project (without going into 50+ project dashboards manually). Hopefully Cloudflare is working on some improvements to that.
KLook at the GraphQL calls that the individual project dashboards are making
