TFixed 
Sorry about that
Sorry about that
Bthanks :)
Bdoes
work for stuff cached by
work for stuff cached by
cache api through workers?
Rhello, does anyone know how to contact cloudflare customer services? it about company's website problem of can't log in to the wp-admin
Ris this the right channel for this?
Rif not, i'm sorry
Bwow
VI created a new Email worker from the Email > Email routing > Email worker. So that's resolved.
Now, I am building a simple ticketing app, but seems like I can't create a wildcard address (ticket-*@example.com) to read all the inbound email on my worker to insert tickets on D1?
The catch-all also doesn't trigger work to read all inbound email on a domain. Any suggestion?
Now, I am building a simple ticketing app, but seems like I can't create a wildcard address (ticket-*@example.com) to read all the inbound email on my worker to insert tickets on D1?
The catch-all also doesn't trigger work to read all inbound email on a domain. Any suggestion?
VThe catch-all works for you with a non-exists address?
I am getting error on Gmail and the email doesn't reach to my email worker. Or how the catch-all works? I am expecting to read all the inbound email on a worker sent to my domain via catch-all or wildcard.
I am getting error on Gmail and the email doesn't reach to my email worker. Or how the catch-all works? I am expecting to read all the inbound email on a worker sent to my domain via catch-all or wildcard.
VWhat you mean by domain doesn't exists ?
I have received many email on a valid address and inserted into my D1, only issue with with catch-all doesn't work for non-exists address.
I have received many email on a valid address and inserted into my D1, only issue with with catch-all doesn't work for non-exists address.
HThat is
ticketdesk.ai. You sent an email to ticketdek.aiHYou forgot the
sdesk
VOops, sorry about that. But same response after correction as well.
VThis is my email worker and code -
HJust to confirm, what if you send an email from an address that isn't blocked?
HIt shouldn't show that error, but maybe...
VThat works fine, I can see message in logs. But the catch-all doesn't work and I need to read all the inbound email and decide to insert / reject on worker. Instead CF reject it before the email is reaching to my worker.
HNo, I meant send an email to
customer-2@ticketdesk.ai from an email that isn't vikash.rathee@gmail.comVOhh, i am not sending from
vikash.rathee@gmail.com, that's not my email id. Just an example in array.
PDo you know if the dart support for workers is any good?
PIt's just that the main works a little like a deprecated JS entrypoint
Pie. the startup script looks like the service workers flow.
Pand also the js bindings are extremely basic
Glet's say i have 10000 active users. And I need to do some jobs for each of them, ideally concurrently. wondering if this is achieveable using cf workers?
i looked at the Limits page, it says the limit is 6 for Simultaneous outgoing
connections/request, that sounds pretty limiting
should i programatically create and deploy many workers so i distribute load among workers?
i looked at the Limits page, it says the limit is 6 for Simultaneous outgoing
connections/request, that sounds pretty limiting
should i programatically create and deploy many workers so i distribute load among workers?
Cit's 6 per invocation/incoming request
CIf your 10k active users all send http requests to your worker at the same time, Workers have no issue handling that load, and each of those requests has 6 Simultaneous outgoing requests it can make
Gwhat does outgoing requests mean?
Glike performing http requests inside of the worker?
Cyea
Cthe docs has really good detail on that: https://developers.cloudflare.com/workers/platform/limits/#simultaneous-open-connections
Gok sounds good, thanks for the help!
Clike allowing customers to cname from anydomain.com -> service.mydomain.com to allow them to use custom domains?
CSounds like you want CF for SaaS: https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/,
https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin/
You have to specifically setup each Customer Domain though, can do it through the API though. For example, all Shopify Custom Domains use CF For SaaS
https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin/
You have to specifically setup each Customer Domain though, can do it through the API though. For example, all Shopify Custom Domains use CF For SaaS
Cloudflare Docs
Learn how to use a Worker as the fallback origin for your SaaS zone.
Canyone know of a way to automatically generate a schema for an openAPIRoute using a sample of json?
Cfor this library @cloudflare/itty-router-openapi
SIf I'm worried about a Worker getting spammed (not a strong concern, just a thought), is there a way to protect against that before it hits the worker to save cost? It's not a huge deal since Workers are inexpensive. But are there options?
CCloudflare Docs
Rate limiting rules allow you to define rate limits for requests matching an expression, and the action to perform when those rate limits are reached.
SAh thank you so much!
SAnyone experienced this issue with email workers before
Unknown error: permanent error (521): 5.5.2 mail.sageee.xyz Error: bare <LF> received?STrying to sent a message to my mail address with
mail.sageee.xyz being my mail server but i do not know why it is not working as sending mails to smth like outlook or gmail does workSThis is my postfix log
Sfixed this
SBut now i have this error
could not obtain a forward upstream: Failed to connect to egress transport: no usable transport when sending mails to a specific mail providerSCan anyone help with this
Gwhy would i need a queue if i can invoke wokers millions of times a day? let's say every day i have 10000 active users each needs to get info from 100 websites. so a worker basically just scrape the info.
in this case can't i just do a 10,000 * 100 for loop to call my worker 1 million times?
in this case can't i just do a 10,000 * 100 for loop to call my worker 1 million times?
CQueues are for more reasons for that,
to start with, you get 1k subrequests per worker invocation, only 6 at one time, and Workers can only call workers up to a certain depth (I forgot what, exactly). The user may disconnect before all your requests are done.
Queues also are for instances where your backend can't handle it at all at once. They let you trade off latency for throughput.
to start with, you get 1k subrequests per worker invocation, only 6 at one time, and Workers can only call workers up to a certain depth (I forgot what, exactly). The user may disconnect before all your requests are done.
Queues also are for instances where your backend can't handle it at all at once. They let you trade off latency for throughput.