• Hello,

    thanks once again for this extraordinary plugin! In my quest to make my domain as fast as possible I upgraded from MariaDB 10.8.3 to 10.9.1 and Gmetrix again but I saw a whooping draw from +80% performance to almost 50% and very law speed ratings.
    I did some digging and saw that MariaDB was not the case but either way I restored the VPS to a snapshot prior state ( done this many times in the past)

    From that moment I cannot get a HIT in my testing for caching and I couldn’t succeed again the desirable 80% speed test in Gmetrix. The caching looks that its king working thought because I have some speed but without rules for example I have exclude form caching the below categories (working like a a charm in the past) and iI was seeing bupass but now all I see is MISS:

    https://sportlive.gr/category/entertainment/
    https://sportlive.gr/category/football/
    https://sportlive.gr/category/football/diethni/

    I check also the cookies (I didnt change anything) and almost disable them ALL! but with no luck. I even removed this plugin, remove the website from Cloudflare and reinstall them all but no luck

    I even migrate it in another VPS but still the same.
    The joke is that my staging environment https://nealive.gr which is a clone of https://sportlive.gr is working like a charm with all plugins cookies etc enabled as in the past. Its like something has locked my primary domain out!

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • hi sir, did you try to inactive all the other plugin and test again?

    Plugin Contributor iSaumya

    (@isaumya)

    Hi @diriras,
    from what I am seeing is that you are seeing MISS because inside the plugin settings under the Cache tab you have either selected the option to not cache category pages or inside the Prevent Following Pages from Caching section you have provided the category URL which basically telling the plugin not to cache these pages and hence it is providing the cache-control header value accordingly.

    Screenshots:

    View post on imgur.com

    View post on imgur.com

    Thread Starter diriras

    (@diriras)

    Hello Saumya,

    You are correct, my setting are in the prevent the following URIs to be cached so that’s why I see MISS in those Categories. But if the caching was working as it should(like in the cloned environment) I should have seen BYPASS like I saw in the last year now.
    https://ibb.co/ccNkpsC

    The problem is not in the excluded categories the problem is that the plugin is partial working and I am trying to find the reason its not logical to work for the full cloned staging and not in the Prod.

    Plugin Contributor iSaumya

    (@isaumya)

    Hi @diriras,
    You are misunderstanding the issue here. You see when you tell the plugin not to cache certain pages, it will add cache-control header value to tell Cloudlfare not to cache those pages.

    Now when cloudflare sees that cache-control header sometimes it returns with the cache status BYPASS while sometimes the cache status will just remain MISS no matter how many times you reload the page.

    But in both cases it is doing the exact same thing – i.e. the page is not being cached by Cloudflare system and instead CF is passing the request to the origin server to generate the page HTML instead of resing it from the cache.

    So, whether it says BYPASS or a constant MISS the outcome is exactly the same.

    Thread Starter diriras

    (@diriras)

    Understood, to be honest I don’t care about the by passing cache pages, its bypassed ok, I care about the MISS value in all my pages cached or not. I don’t see HIT any more to none of my pages! But the caching seems to work

    Plugin Contributor iSaumya

    (@isaumya)

    I also have been seeing something similar on some of my client websites where despite a page being served from Cloudflare CDN cache it constantly shows the cache status as MISS.

    I think this is because some sort of bug/issue at cloudflare end. But to check if your page is being served from the cache don’t look at the cache-status header value. Intead in the response header if you see something like age: with a number associated with it. That means the request is being served from cache. The age value denotes since how many seconds it has been in the cache.

    Also, you can look at the TTFB number. So, if page is being served from cache TTFB will be very low.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘cache miss but its working’ is closed to new replies.