Codex
Explore posts from serversCDCloudflare Developers
•Created by Codex on 6/20/2024 in #workers-help
K6 load testing and 429s
So interestingly, it appears that we get the 429 as a result of the subrequest opposed to the top level request.
Security > Events
The services (Azure Functions) being hit by the worker work perfectly when hit directly, but we start seeing the 429s when the worker is involved (CF Worker -> Azure Functions). These subrequests are where we're observing 1015s
Security > Events doesn't appear to have any security events matching that description, so something else perhaps.
Regardless though, we'll put something through to CF support and go from there.13 replies
CDCloudflare Developers
•Created by Codex on 6/20/2024 in #workers-help
K6 load testing and 429s
Great to know, thank you!
13 replies
CDCloudflare Developers
•Created by Codex on 6/20/2024 in #workers-help
K6 load testing and 429s
yeah that's where I got to, just clarifying what I have read and done to this point :)
13 replies
CDCloudflare Developers
•Created by Codex on 6/20/2024 in #workers-help
K6 load testing and 429s
Ah awesome, will do, thank you
13 replies
CDCloudflare Developers
•Created by Codex on 6/20/2024 in #workers-help
K6 load testing and 429s
I was reading through this documentation too: https://developers.cloudflare.com/workers/runtime-apis/bindings/rate-limit/#rate-limiting
But
Rate limits that are applied after your Worker starts suggests this isn't where I want to be lol13 replies
CDCloudflare Developers
•Created by Codex on 6/20/2024 in #workers-help
K6 load testing and 429s
Thanks for that, so I've read that and while it talks to a lot of the implicit limitations on free tiers and makes mention of handling 429's if you're programatically hitting the worker like:
I'm still failing to see how I can outright disable this protection measure or whitelist specific IPs while this testing is being performed
13 replies