tomypro80
CDCloudflare Developers
•Created by tomypro80 on 6/11/2024 in #general-help
Is there a way to "warmup" an email that is configured and forwarded through Cloudflare's catch-all?
Services like instantly.ai expect your email to either be managed by Google et al or have POP3/IMAP credentials; is there a way to warmup an email that is managed through Cloudflare's catch all rules I am not thinking about? I am on the fre tier.
2 replies
CDCloudflare Developers
•Created by tomypro80 on 6/2/2024 in #general-help
Configure an email catch-all route *@domain.com for my 300+ domains to a single email by API?
Is this currently possible? Using the interface it seems I need to define the email alias per domain explicitly vs a general wildcard.
2 replies
CDCloudflare Developers
•Created by tomypro80 on 5/31/2024 in #workers-help
Is it expected that my workers log every request URL they get executed for?
Is it expected that my workers log every request URL they get executed for? What is the easiest way to write to the logs in the UI dashboard view or is that not possible? console.log does not do the trick and we have not setup wrangler successfully yet. Is there an alterantive or is wrangler the way to go?
6 replies
CDCloudflare Developers
•Created by tomypro80 on 5/30/2024 in #general-help
Fastest practice to 410 a regex URL pattern not supported by worker routes?
I have a URL pattern for which I want to return the fastest possible static 410 response (to remove them from the Google index). However, the pattern can not be expressed with the limited pattern support for Cloudflare Workers.
What is the best way to configure this in Cloudflare? I could think of putting a rewrite rule in place that forwards to the same /410 page that then delivers the 410 response from the edge without ever hitting the origin.
Is that the best approach though?
1 replies