yes, the point is that i'm trying to process the e-mail with code and the e-mail address woudl conta
yes, the point is that i'm trying to process the e-mail with code and the e-mail address woudl contain the user id
Pso trying to find an easy way to do that, email workers seemed like a good option
HWould it work if you put it on a subdomain?
Pi think you can't setup catch-all for subdomains, on cloudflare at least
P"Catch-all rule only applies on the zone-level domain, you can’t create catch-all rule for each of your subdomain."
HWhat if you set a forward in Zoho, toward a subdomain? So forward to auto@sub.doma.in?
Pdamn, turns out theres webhook support in zoho mail itself
HWell, that works too!
P
HMaybe startsWith instead of contains?
Pyeah i'll got it from there, thanks. Anyway, feature request: support wildcards for email workers routing 
CYou can use a wildcard catch-all, and then parse the email address out
CCatch-all would apply to subdomains but you can't configure per subdomain, if that makes sense. You could just add a subdomain and not your root domain to email routing, or just handle it all through a worker
Pbut if i enable catch-all, i need to update the mx records to cloudflare's server, no? In that case i would lose access to Zoho Mail.
CIf you wanted emails for your apex/root (email@domain.com) to go to Cloudflare, yea you'd have to pick one or the other. Could just use a subdomain though (email@sub.domain.com)
Cthat's a limitation in just how email works
Psubdomain would be fine, but it says "Subdomains are dependent on domain. If domain is disabled, subdomains will be disabled too." on the email routing settings screen(where it displays what MX records i need to setup)
Por i should just ignore that and set up the cloudflare mx records for a subdomain?
Cannoyingly that's still wrong in the ui. It's indeed not true, just tested again now, you can receive mail on subdomains without enabling the domain itself
Cyou can just add a subdomain under Email routing settings, it'll do the records for you
HHello, does anyone knows if I can install a non js dependency in Workers Build ? I tried adding a build variable
Edit : Figured it out, using
UNSTABLE_PRE_BUILD
curl -fsSL https://d2lang.com/install.sh | sh -s -- but it's not working like it did with Pages beforeEdit : Figured it out, using
SKIP_DEPENDENCY_INSTALL and modifying the build command to install and export the PATH before running the js deps install and build works, altough not very ergonomic.
PSo basically i setup a subdomain with cloudflare MX, setup catch-all and since the MX is only on the subdomain, it will only catch-all the subdomain email address, which then i can forward to a worker. In theory this could work.
Cdoes pages not support
envlike do I need to juggle multiple toml files for different pages sites out of my same repo ?
P"An EmailEvent is the event type to programmatically process your emails with a Worker. You can reject, forward, or drop emails according to the logic you construct in your Worker."
How do i drop? I don't see an example for that.
How do i drop? I don't see an example for that.
CCloudflare Docs
An EmailEvent is the event type to programmatically process your emails with a Worker. You can reject, forward, or drop emails according to the logic you construct in your Worker.
PI can only see reject, forward or reply. I just don't want to do anything with it. Just return false from the worker?
CI believe if you just do nothing it would get "dropped". Worth noting the dashboard shows all emails handled by Workers as "dropped" regardless of what you do with it
Cthere's no return
Pgot it
UWhen I added a custom domain to my CF worker It changes host name in the browser URL. Url for my worker is https://wf-worker.support-c31.workers.dev/ However, I have added this custom domain wfweb.whoisfreaks.com. Attached is an image of worker code. PLease look into this issue.
Image
Image
WhoisFreaks
WhoisFreaks provides Live and Historical domain records through downloadable WHOIS Database and WHOIS APIs in REST JSON and XML format.
HI'm not sure I understand what the issue is. Can you try explaining a bit deeper?
Kanyone know if i can run wrangler with astro so it rebuilds on dev?
U@Hard@Work Previously, I have 3 application two of them are dynamic and one is static and all three of them were on a single domain. Now I want to use CF pages for my static website. and two application remains intact. Then I have added subdomains for other two applications and used a worker to route traffic to all three applications but issue is that my CF worker is changing host.
When I type
When I type
https://wfweb.whoisfreaks.com/tools/whois/lookup ideally this url remains same in the browser but it changes to https://tools-cf-worker.whoisfreaks.com/tools/whois/lookupU@Hard@Work my worker works fine with it's original URl
https://wf-worker.support-c31.workers.dev/ IN this case when I go to https://wf-worker.support-c31.workers.dev/tools/whois/lookup my host does not changes. This issue occurs when I add a custom domain to that worker.
Lis this outdated?
LI saw CF Pages now also suports Static Assets for the most part
INo. Assets for Workers are still in beta.
IPages and Assets are two different things.
LI meant the "it may be supported in Cloudflare Pages" sentence in the card.
IAh. Assets is fairly feature-complete but Pages still has certain things that aren't in Static Assets (such as _routes.json or path-based routing)
LMaybe I remember things wrong.
LI'm pretty sure when the feature was launched last September, it was only available for Workers
LThe Cloudflare Blog
To celebrate Builder Day 2024, we’re shipping 18 updates inspired by direct feedback from developers building on Cloudflare. This includes new capabilities, like running evals with AI Gateway, beta products like Queues and Vectorize graduating to GA, massive speed improvements to KV and Workers AI, pricing simplifications, and bringing key featu...
II think you're confusing things. What that doc line means is that they are two different products, with Workers Assets being the newer (preferred) version, but Workers Assets is in beta and so some things in Pages may not be in Workers Assets yet.
LIs there any reason to prefer Pages once all features are supported by Workers?
INo, not really.
IAnd Pages will likely (eventually) be deprecated, but it's not at the moment.
LI thought so.
LProvides information about using runners with AWS CodeBuild.
