Hello!
My site has an active Cloudflare account and is showing “Verified by: Google Trust Services” instead of “Verified by: Cloudflare, Inc”, which was previous the case. Also when I inspect the elements in the Console it shows cf-cashe-status: MISS.
Can you please help me with resolving this issue. Why is the status not HIT and why it doesn’t show “Verified by: Cloudflare, Inc”.
Thanks!
Cacheable files aren’t necessarily cached forever.
Even if you choose to set a cache time of 10 years, it only means “you MAY cache it for up to this time”, and even that doesn’t guarantee that anyone is able to honour that request, for example due to storage capacity.
You can try enabling Tiered Cache, to improve your cache HIT ratio.
→ https://dash.cloudflare.com/?to=/:account/:zone/caching/tiered-cache
In the past, Cloudflare did use DigiCert quite a lot for issuing certificates, and many of those were issued through an intermediate certificate chain, which may have appeared in browsers, as if it was issued by Cloudflare.
The use of these DigiCert certificates has been deprecated.
Thank you!
I will definitely look at enabling Tiered Cache and see if this can resolve it!
Will Purge Cache – > Purge Everything eventually also help in this case?
Note: Depending on your Cloudflare plan, as well as how you access / cache the content, you may be in violation of the Cloudflare ToS.
→ Service-Specific Terms → Application Services → Content Delivery Network:
That being said:
I guess it depends what is needed to resolve it in your opinion. 
While playing around with Tiered Cache a while back, I was actually able to keep a test file in Cloudflare’s cache for several days.
Cache-Control headers were asking Cloudflare to cache it for 24 hours / 1 day, but even after those 24 hours, Cloudflare simply sent another tiny request to my origin, in order to re-validate the cache, asking whether the file had been modified, which my origin simply returned the HTTP status 304 Not Modified to.
These re-validation requests ending up in 304 Not Modified were very minimalistic, and not actually fetching the full file’s size from the origin again.
Mixing requests over multiple regions even showed that requests from both Denmark (Europe), France (Europe) and very distinct regions such as e.g. Canada (North America) were retrieving the cached file, and that Cloudflare was not actually contacting the origin within the 24 hour window defined by the Cache-Control header.
The origin (a machine in Denmark) only saw the requests (one full request downloading the full file, two or three very limited re-validation requests over the period (one after each 24 hours window had passed away)) as coming from Cloudflare’s datacenter in Hamburg (Germany).
So, if you are looking to maximize the cache results as CF-Cache-status: HIT, I would definitely recommend to try Tiered Cache.
The final result may however vary, depending on both what your origin (e.g. Cache-Control headers) as well as eventual other Cloudflare cache settings (e.g. in the Dashboard) are set to.
If you want Cloudflare to cache your files (e.g. return CF-Cache-Status: HIT), then no, then you need to keep your hands off that purge cache thing.
Purging the cache (individual files, or everything), literally means that Cloudflare will delete the cache, and that CF-Cache-Status will return to MISS.
Thanks for your reply!
I enabled Tiered Cache so we will see what will come regarding the CF-Cache-status: HIT (yes, this is what I mean under resolve).
I am really still not sure about why the site shows Google Trust Services and not Cloudflare? It was “Cloudflare, Inc” when I created my Cloudflare account (about 1,5 years ago) and it changed a couple of months ago to Google Trust Services.
Should that bother me in any way?
Cloudflare is not, nor never has been a certificate authority. They do not issue their own certificates, they rely on partners who may display the exact details differently… but Cloudflare is not the issuing CA.
Cloudflare works with a few CA to issue certificate to our Customers and Google Trust Services is one of them, so nothing to worry about here.
We don’t cache everything unless told to. You can see our default take on cache here:
Check this out:
Thank you!
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.