Browser Caching values too agressive

  • Resolved spingary

    (@spingary)


    5 years ago

    Would it be possible to add the ability to change the Browser Caching expiration periods? The defaults are too aggressive, in my opinion.

    For example, the default expiration period for all HTML pages is 6 months:

    
ExpiresByType text/html                             "access plus 6 months"

    If a user visits the blog listing page today, and then tomorrow I added a new blog, that user won’t see the new blog in the blog listing page for 6 months unless he/she clicks the refresh button on the browser. Not even if the browser program was closed and restarted. (I’ve tested this.)

    WP-Rocket has that default set to 2 days, by the way.

    It’d be really nice if some of the periods can be changed in the SG-Optimizer plugin settings.

    Thank you.

    • This topic was modified 5 years ago by spingary.
Viewing 1 replies (of 1 total)
  • Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    WP Rocket use static html files for their caching that are loaded through an .htaccess rule whenever they exist. This is how their caching works so they need short default borwser caching values.

    The SG Optimizer uses much more sophisticated method of caching – our NGINX reverse proxy which is controlled by headers. That’s why we can and we are setting those default caching periods high according to the Google recommendations. We do set the appropriate last modified headers which instruct the browser to reload the asset when it is updated.

    To summarize, the behaviour you’re explaining is caused by not properly setting the last modified header for that page. If you’re using WP Rocket, please contact their support to see why the proper headers aren’t set when the page is modified. If you’re using the SG Optimizer – please provide me with your site URL so I can troubleshoot further, the default browser caching values do not lead to such behaviour and there’s something else causing it.

Viewing 1 replies (of 1 total)
  • The topic ‘Browser Caching values too agressive’ is closed to new replies.