Cthat's a good number
Wnot yet, rapid reset was hitting 200 mil rps though
Wso i'm sure we'll see a ddos hit that within the next 2 years
Acan I use redis inside a worker ? does it support these protocols ?
JHello anyone can you please help me I forgot my email which I have used for cloudflare, my domain purchased from godaddy and in name server I have cloudflare name servers, so I want to know my cloudflare email, can you please guide me how to get email
�hey everyone, what does Execution Duration mean? As in 10 GB-sec
HThis?
Cloudflare Docs
Diagnose issues with Workers metrics, and review request data for a zone with Workers analytics.
HIt isn't as relevant anymore, as only Durable Objects still bill on GB-sec
�ah, I'm just curious if it's showing the speed at which requests are received/responded, as in 80Gbps
HI don't think there are metrics for that?
�so pretty much execution duration is useless
�it doesn't show anything that can show the performance or anything useful
HWell, now it is, but before it was a billable param, so it was useful
�ohhh
�what happens if you reach request limit?
�how can I detect it, what status number is shown...
�ok figured out
� if it fails
IThe
ok field simply checks if the status is 200 (which it won't be if you're out of requests) so yes, that will work.
GHi!
About the workers subrequests limits (1000 for paid plan), if we need more, could we uses the last subrequests to trigger this same worker to continue ? ( or using a 3rd-party FaaS to loopback to the CF worker if required )
Queues or DurableObjects + Alarm seems to be very heavy works and money to just call 2 or 3 times a worker to finish some subrequests call
About the workers subrequests limits (1000 for paid plan), if we need more, could we uses the last subrequests to trigger this same worker to continue ? ( or using a 3rd-party FaaS to loopback to the CF worker if required )
Queues or DurableObjects + Alarm seems to be very heavy works and money to just call 2 or 3 times a worker to finish some subrequests call
HI would go with a Service Binding, but yes
HThough note there is a maximum depth of binding calls you can make
GThank you for your advice. I'll give a look to Service Binding!
몰There is a suggestion in the mail binding function of Service Worker. In Mail Metric, I would like it to be divided into processed, forwarded, lost, and other errors.
I am planning my own mail consultation service that does not forward mail data and processes it only with Cloudflare's functions. Here, we confirmed that it was saved in the DB, but we confirmed that it was processed as lost in the statistical data. Or, I want to know if there is a function that tells me that it was processed properly, but I couldn't find it.
I am planning my own mail consultation service that does not forward mail data and processes it only with Cloudflare's functions. Here, we confirmed that it was saved in the DB, but we confirmed that it was processed as lost in the statistical data. Or, I want to know if there is a function that tells me that it was processed properly, but I couldn't find it.
GHi! There is a solution to known how many subrequests have been already used inside the current Worker ( to known if next subrequests are allowed ) ?
GOk thank you! I'll just do a little wrapper to all my external calls ( d1, fetch, etc ) to count them manually
Shi - we noticed when using the Rate Limit api/binding for workers that the rate limit never seemed to trigger for IPv6 traffic. It only triggered for IPv4 traffic. This was tested using cf-connecting-ip and x-real-ip. Is there a different header or method we can use to reliably rate limit by IP? Not sure if our IPv4 settings for the site are causing the issues.
SWe are aware that shared IP's is a common issue with rate limiting per IP, for our use case this is not an issue.
Adoes
pnpm wrangler login support being used from within a devcontainer by pasting the consent link on a local browser?Athe localhost:8976 port forward is created by vscode
Athe consent page remains on the "allow" animation until wrangler timesout
Aand I see a CORS error on the console
Ais there a way to check if wrangler's http server is actually working?
Ahttp://localhost:8976/ itself keep waiting for a response
Acurl -I works thoughAI tried with a fresh repo and fresh container and the exact same happens
Ais there a level beyond WRANGER_LOG=debug?
Athis is interesting:
not listening ipv4?
not listening ipv4?
A(that's within the devcontainer)
A[dev]\nip = "127.0.0.1"\n on wrangler.toml
it's still only listening ::1Ait did fix
wrangler dev
JHow come it says the environment is production on my staging worker? I have created two environments in my wrangler config, production and staging. This is the worker that was created when I specified deploying to staging. Is this environment at all related?
HAnyone know a timeline on getting this fixed? Sucks to not have: https://developers.cloudflare.com/workers/platform/known-issues/#custom-ports
Cloudflare Docs
Known issues and bugs to be aware of when using Workers.
JI would not expect the handling of custom ports to change in the foreseeable future - it's been this way for years. If you control the server you're hitting, your beset bet is going to be to just run on 443 or 80.