[sladey]

I'm a big supporter of Cloudflare and have been using it for almost 8 years. I personally don't think doing something like that is what Cloudflare needs.

What Cloudflare needs is further customization, especially in regards to caching. We actually had to migrate a certain part of our infrastructure to Fastly due to the lack of caching customization/rules.

I'd like to see:

- Custom caching rules similar to the new firewall rules

- Finer granularity of the cache expiry (I'm aware Enterprise has the ability to cache for 30 seconds, but we don't want to upgrade to Enterprise just for that one thing).

- Cache hit rate analytics grouped by path/domain/etc

[kmf]

FWIW, our Workers product is pretty good at allowing you to define custom caching rules. We have a section in the Workers docs specifically focused on the Cache API: https://developers.cloudflare.com/workers/reference/cache-ap...

If that doesn’t help you build what you’re looking for, happy to chat via email and hear more about what you need: kristian@cloudflare

[skunkworker]

I've submitted suggestions to some people but I believe with the workers it should be possible to create your own custom pull/push CDN because of the granularity controls they have added. It used to not be possible to interact with the caching layer but since they have added controls for that (about a year or so ago)

Also your link is missing a trailing slash (which is odd that their router doesn't add that). https://developers.cloudflare.com/workers/reference/cache-ap...