cf-cache-status:HIT even using the ?swcp=1 busting parameter

  • Resolved JulioRos

    (@julioros)


    1 week, 3 days ago

    The problem im facing is that, after clearing the cache, new users get the right (last version) js scripts (working ok), but when i visit the site (logged in and using the busting parameter!!), i get the deprecated js versions. i checked that i get a HIT in the cache headers even using the parameter. FYI, the scripts i mention use control version parameters also.
    Im on cloudways with varnish set to be cleared when cloudflare clears cache.
    i tried: “Add browser caching rules for static assets” activated and deactivated, also disk cache, but no results. It would help if plugin have some detailed instructions somewhere.
    Could you guide me where can be the issue so that i can get the updated scripts versions? thanks (as its a live ecommerce, i guess returning customers visiting the site will face the same issue and its not a good solution for me to ask them to clear the browser cache)

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Ionut Neagu

    (@ionutn)

    Hey,

    Ideally I would need the url to debug this, first I need to understand if the issue is with disk or cloudflare cache. In the latest version the cache busting parameter is not needed, the wp-admin is not cached by default and there are various cookies/urls that are also not cached.

    If you get HIT and you don’t want, make sure you add the url/cookie in the textarea.

    Thread Starter JulioRos

    (@julioros)

    thanks. i had get rid of the cache cache busting parameter. Im facing the issue that some changes i made to pages are cached in my browser! (i guess as after clearing cache and testing the page on other browsers i see the correct page, but on the no cache page it shows the former page). Its like if the cache is correctly recreated but when not using the cached page i see the former version. its driving me crazy. Page URL : https://www.cuchicuchi.es.

    Cloudways hosting, settings:

    Add browser caching rules for static assets: YES

    Overwrite the cache-control header for WordPress’s pages using web server rules: NO

    Save response headers: YES

    Plugin Support Ionut Neagu

    (@ionutn)

    Hey,

    You can disable the caching in the browser, this is how it usually works and is not related to the plugin, the browsers would hold various files in cache.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.