Can you CNAME to a [name].workers.dev worker?

[Judge]

The main reason you can’t just CNAME to any Cloudflare subdomain (workers.dev or not) is that doing so would require Cloudflare to set up an IP address specifically tailored to handling that worker but with any incoming SNI/HOST header. Without a special IP, the incoming request just looks like any other regular Cloudflare request, since CNAMEs just alias IP addresses and don’t instruct the client to do something like request the CNAME target but instead display the content as the original hostname.

As for hitting the CF cache first, the Workers technical lead himself explained why you can’t just cache in front of the worker to get cheaper Workers pricing:

Cache in front of Worker

So, I think this thread is conflating technical architecture with pricing… A Worker can use the Cache API to implement arbitrary caching logic. A Worker that makes good use of the Cache API should be able to achieve the same performance as if the cache ran in front of the Worker. Hence, there is not a technical reason for Workers to run behind cache. But it sounds like the motivation here is to avoid being billed for requests that hit cache. This assumes that if cache ran in front of Workers, …