CF-Cache-Status: HIT

  • Something I don’t quite understand. When I check headers on any web site where I have installed this plugin I see this first load:

    CF-Cache-Status: MISS

    Then if I retest by loading the page into the header tester again (hackertarget.com for example) I see

    CF-Cache-Status: HIT

    It will then remain a HIT if I keep retesting all day long.

    Then if I go to say webconfs.com which is another tester, I get

    CF-Cache-Status: MISS

    I retest and I get a HIT. It will also remain a HIT thereafter.

    Not sure why as I have preloading in the plugin set to on. Is it meant to be doing this? Is it because of different locations being used and the page is being served from different cloudflare servers at the edge ?

    • This topic was modified 3 years, 8 months ago by frenchomatic.
Viewing 3 replies - 1 through 3 (of 3 total)

  • The websites you are using to check headers might be in different geographical locations, so hit a different cloudflare datacentre where the content is not cached.

    If you look at CF-Ray the last three letters are the location.

    Thread Starter frenchomatic

    (@frenchomatic)

    Yup – as you have confirmed. Cloudflare appears to cache on a second load from any edge server so it is a pull model. I am not sure what the point of preloading is if this is the case as there are so many locations?

    Plugin Contributor iSaumya

    (@isaumya)

    If you like to take a super deep dive on how Cloudflare cache works, I would recommend checking out this article: https://acnam.com/untold-truths-of-cloudflare-cdn/

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘CF-Cache-Status: HIT’ is closed to new replies.