Title: How do I completely avoid browser cache for HTML?
Last modified: January 29, 2025

---

# How do I completely avoid browser cache for HTML?

 *  Resolved [Gulshan Kumar](https://wordpress.org/support/users/thegulshankumar/)
 * (@thegulshankumar)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/how-do-i-completely-avoid-browser-cache-for-html/)
 * Dear LiteSpeed Cache Plugin developer,
 * I hope this message finds you well. We have recently observed that our homepage
   is being cached in the browser for **7 days**, which is unexpected given our 
   site updates every 5-10 minutes during working hours. While it’s acceptable to
   store page cache internally for 7 days, caching in the browser is causing issues
   due to the frequent updates.
 * As a temporary measure, I modified the `.htaccess` [code](https://gist.github.com/thegulshankumar/3d11411f3e75ac2f048988567c1ed3fc#file-ls-cache-settings-txt-L833)(
   linked to gist) to disable the browser cache. However, I would appreciate your
   assistance in providing an appropriate solution to ensure proper cache management
   without affecting the page’s update frequency.
 * Thank you for your attention to this matter. I look forward to your prompt guidance.
 * Best regards,
   Gulshan Kumar

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

 *  Plugin Support [litetim](https://wordpress.org/support/users/litetim/)
 * (@litetim)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/how-do-i-completely-avoid-browser-cache-for-html/#post-18273094)
 * [@thegulshankumar](https://wordpress.org/support/users/thegulshankumar/) 
   have
   you tried disabling: [https://docs.litespeedtech.com/lscache/lscwp/cache/#browser-tab](https://docs.litespeedtech.com/lscache/lscwp/cache/#browser-tab)
   this setting?
 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/how-do-i-completely-avoid-browser-cache-for-html/#post-18273409)
 *     ```wp-block-code
       SetEnvIf Request_URI "/$" change_headerHeader set Cache-Control "no-cache, no-store, must-revalidate, max-age=0" env=change_header
       ```
   
 * assuming all of your pages are ending with `/` in URL , then please try this 
   code snippet
 *  Thread Starter [Gulshan Kumar](https://wordpress.org/support/users/thegulshankumar/)
 * (@thegulshankumar)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/how-do-i-completely-avoid-browser-cache-for-html/#post-18273731)
 * **I believe this issue is not related to LiteSpeed cache. **
 * The `<IfModule mod_expires.c>` block appears to have been added in an unusual
   way within the `# BEGIN WordPress` section. It is highly unlikely that LS Cache
   added it this way. Most likely, another developer added this code intending to
   improve performance but inadvertently ended up caching HTML incorrectly.
 * **Here’s how I fixed it.**
    - Removed the entire entries of .htaccess except the default rewrite rules of
      WP.
    - Clicked “Reset” button in the LiteSpeed. I love this reset button, it usually
      set the SAFEST settings for my site.
 * Thanks

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

The topic ‘How do I completely avoid browser cache for HTML?’ is closed to new replies.

 * ![](https://ps.w.org/litespeed-cache/assets/icon-256x256.png?rev=2554181)
 * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/litespeed-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/litespeed-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/litespeed-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/litespeed-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/litespeed-cache/reviews/)

 * 3 replies
 * 3 participants
 * Last reply from: [Gulshan Kumar](https://wordpress.org/support/users/thegulshankumar/)
 * Last activity: [1 year, 4 months ago](https://wordpress.org/support/topic/how-do-i-completely-avoid-browser-cache-for-html/#post-18273731)
 * Status: resolved