Title: Leverage Browser Caching Issues
Last modified: July 12, 2021

---

# Leverage Browser Caching Issues

 *  Resolved [kranzoky](https://wordpress.org/support/users/kranzoky/)
 * (@kranzoky)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/leverage-browser-caching-issues-2/)
 * 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 4 years, 11 months ago by [kranzoky](https://wordpress.org/support/users/kranzoky/).

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Ahmed Kaludi](https://wordpress.org/support/users/ahmedkaludi/)
 * (@ahmedkaludi)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/leverage-browser-caching-issues-2/#post-14655366)
 * 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](https://wordpress.org/support/users/kranzoky/)
 * (@kranzoky)
 * [4 years, 11 months ago](https://wordpress.org/support/topic/leverage-browser-caching-issues-2/#post-14655553)
 * 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](https://wordpress.org/support/users/ahmedkaludi/)
 * (@ahmedkaludi)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/leverage-browser-caching-issues-2/#post-14664259)
 * 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.

 * ![](https://ps.w.org/accelerated-mobile-pages/assets/icon-256x256.png?rev=1693616)
 * [AMP for WP - Accelerated Mobile Pages](https://wordpress.org/plugins/accelerated-mobile-pages/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/accelerated-mobile-pages/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/accelerated-mobile-pages/)
 * [Active Topics](https://wordpress.org/support/plugin/accelerated-mobile-pages/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/accelerated-mobile-pages/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/accelerated-mobile-pages/reviews/)

## Tags

 * [cache](https://wordpress.org/support/topic-tag/cache/)
 * [caching](https://wordpress.org/support/topic-tag/caching/)
 * [headers](https://wordpress.org/support/topic-tag/headers/)
 * [setting](https://wordpress.org/support/topic-tag/setting/)

 * 3 replies
 * 2 participants
 * Last reply from: [Ahmed Kaludi](https://wordpress.org/support/users/ahmedkaludi/)
 * Last activity: [4 years, 10 months ago](https://wordpress.org/support/topic/leverage-browser-caching-issues-2/#post-14664259)
 * Status: resolved