Well…kind of. Cloudflare doesn’t have infinite cache, and it has a lot of datacenters. Frequently accessed data stays in the cache longer. Standard cache duration is less than a day, I believe. Maybe just a couple of hours. This is great for high-traffic sites. If you’re a low-traffic site, then the load on your server is minimal in the first place.
You can set up some Page Rules to set longer Edge Cache durations, but that file will still get purged sooner if it’s rarely accessed.
I’ll see your expansion, and raise you one. I believe Google is only looking at cache expiration headers, and not Cloudflare HIT/MISS. So if you’ve at least set an extended cache duration, Google will be happy.
I have a web home server with some zip, rar, and other files. I have 20mbps of upload speed.
If I want to distribute files hosted in my home server to users, I need more than only 20mbps, and so I thought to Cloudflare.
So my server will upload the files only once to Cloudflare proxies, and they will distribute the files to the clients.
This service sounds like a web hosting, because Cloudflare will distribute the files, not my server.
I can increase the cache time, and this is all available in free plan.
It’s sort of the opposite. Clients will request a file from Cloudflare. Cloudflare will go get it from your server. Cloudflare serves the file to the client, and saves a copy in it’s cache for the next client. On a per-POP basis.
And I didn’t yet activate the http proxy for that DNS.
When I will activate the proxy (orange cloud) this rule will take effect.
All requested from that DNS will be catched in Cloudflare POP for 1 month and in clients’ browsers for 1 day.