Leverage Browser Caching Issues

  • Resolved kranzoky

    (@kranzoky)


    3 years, 4 months ago

    I recently was having issues with “Leverage Browser Caching” being enabled on the plugin and causing our blog/news site to display outdated content.

    After going through some bug detecting and realizing the plugin was overriding our default expiration headers, I am wondering why “leverage browser caching” wouldn’t be enabled just for AMP pages and not the site as a whole?

    • This topic was modified 3 years, 4 months ago by kranzoky.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Ahmed Kaludi

    (@ahmedkaludi)

    Can you please help us to check your issue? Please share the URL of the website. So that we will check and get back to you. And also Can you please check it once by disabling Leverage Browser Caching temporarily and check if it happens the same or not?

    Thread Starter kranzoky

    (@kranzoky)

    I already resolved the issue, but it was due to the cache-control max-age that was set by “leverage browser caching” being enabled and it was set to 90 days. However, it was setting that max-age header for our whole site (even non amp version) and not just for AMP version. I would assume when enabling that setting that “leverage browser caching” would only be enabled for AMP versions of the pages and not non AMP versions.

    Plugin Author Ahmed Kaludi

    (@ahmedkaludi)

    If you enable that, It would be applied to the whole site both AMP & Non-AMP. Because it needs to done from htaccess and their we can’t control the amp vs non-amp detection.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Leverage Browser Caching Issues’ is closed to new replies.