I would go with a Service Binding, but yes
I 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 ) ?
HAfaik no
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 -II 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.
HGot it, thanks. There's some pretty valid use cases for not using 443 or 80 and it's not uncommon for systems that handle logging/monitoring or data ingestion.
Lots of things, like this, custom CAs, and fetch to a specific IP, are easy to overlook when evaluating using workers. Everything we put on Cloudflare works amazingly but any non-basic integration with external system sucks almost enough to not use workers. Hope to see more answers than just migrate those services to Cloudflare in the near future.
Lots of things, like this, custom CAs, and fetch to a specific IP, are easy to overlook when evaluating using workers. Everything we put on Cloudflare works amazingly but any non-basic integration with external system sucks almost enough to not use workers. Hope to see more answers than just migrate those services to Cloudflare in the near future.
JIs there something equivalent to the pages plugin for cloudflare access that I can use in a worker? https://github.com/cloudflare/pages-plugins/tree/main/packages/cloudflare-access
RHey, what's the pricing for websockets but without durable objects? Like if i connect from a websocket worker to another websocket, that will count as wall time, right?
HYes, though note that Wall Time is no longer billed, only CPU time
HAnd also, if you aren't using the Durable Object WebSocket Hibernation API, then active connections may be shut down if the runtime evicts your Worker(which is more likely to happen after 30 seconds).
RSo i should connect to the second websocket from the hibernation api, right?
HHibernation is only supported for inbound WebSocket connections, if that is what you mean
Ri think so 
, i will give it a try, thank you 
, i will give it a try, thank you 
CHas it been resolved?
CAlright, it’s weird
BAnyone experience here with connecting through RDS from a worker through a Cloudflare tunnel? Not looking to use Hyperdrive, since that doesn't have support for tunnels yet
Kwhat's everyone using for SMTP nowadays, I used to use AWS SES a lot, still do sometimes but I really was hoping Cloudflare would release something for transactional emails that links with Workers like D1/KV etc with bindings
USES is the best option
KSES OK, fast, deliverability usually great, however I find that some of the other providers give you a lot more in terms of logging, open tracking and overall a nicer experience for debugging issues
USES has everything one could possibly need and is priced way better than everything else imo 
SES -> Firehose -> Pretty much anywhere for all the logging you could need
SES -> Firehose -> Pretty much anywhere for all the logging you could need
SIs there a variable that can be checked to determine if workers is running on a local dev environment versus in the deployed cloudflare env ?
SSo.. I saw the blog about python in cloudflare workers... Is it really just for local development still? 
I can't seem to even get the example one to deploy.
I can't seem to even get the example one to deploy.
Μisn't there a way to deploy a worker directly from a github repo like pages does?
NI'm using this GitHub action https://github.com/cloudflare/wrangler-action and it works perfectly for that
GitHub
easily deploy cloudflare workers applications using wrangler and github actions - cloudflare/wrangler-action
easily deploy cloudflare workers applications using wrangler and github actions - cloudflare/wrangler-actionΜthank you
JHi Folks,
I am implementing A/B split test on workers and i am following the documents of this --> https://developers.cloudflare.com/reference-architecture/diagrams/serverless/a-b-testing-using-workers/
Here i have integrated in worker, everything seems fine other than
let cookie = request.headers.get("Cookie")
cookie always return --> token=453453453453453 some random number.
I am expecting the cookie which is set on browser.
Kindly do needful
Thanks
I am implementing A/B split test on workers and i am following the documents of this --> https://developers.cloudflare.com/reference-architecture/diagrams/serverless/a-b-testing-using-workers/
Here i have integrated in worker, everything seems fine other than
let cookie = request.headers.get("Cookie")
cookie always return --> token=453453453453453 some random number.
I am expecting the cookie which is set on browser.
Kindly do needful
Thanks
Cloudflare Docs
A/B testing, also known as split testing, is a fundamental technique in the realm of web development, allowing teams to iteratively refine and …
Μwhat is the best way to run my app in cloudfare? i have a python fastapi but it uses pandas and actually trying to manually compile it to waasm is way too complicated
Dif i put a console.log into a worker, how do i see the result? would it be shown in npx wrangler tail?
NThat should be possible according to the doc https://developers.cloudflare.com/workers/observability/logging/real-time-logs/
Cloudflare Docs
Debug your Worker application by accessing logs and exceptions through the Cloudflare dashboard or
wrangler tailthanks. that's what i was thinking. i'm not seeing the results though. not sure why. i probably did something wrong somewhere. will do some more troubleshooting.