• Hi, I have 2 websites where the leverage cache is not working for images png or jpg, it happened recently we are seeing it on the new pagespeed
    they said this should be the directive Cache-Control: max-age=31536000
    but even changing it on the HTACCESS won’t make the warning go away for those assets, can you help? it’s the plugin?

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Emre Vona

    (@emrevona)

    can you tell me the url please? Are you using Nginx or Apache?

    Thread Starter mhoney

    (@mhoney)

    Hi sure thing
    Nginx proxies requests to Apache. But it’s Apache that’s handling PHP-FPM

    It was working before, not sure if it was last update of the plugin

    • This reply was modified 6 years, 1 month ago by mhoney.
    • This reply was modified 6 years, 1 month ago by mhoney.
    Thread Starter mhoney

    (@mhoney)

    Nginx proxies requests to Apache. But it’s Apache that’s handling PHP-FPM

    Plugin Author Emre Vona

    (@emrevona)

    you are using Nginx as I see. Please take a look at the following tutorial.

    https://www.wpfastestcache.com/tutorial/how-to-enable-leverage-browser-caching-on-nginx/

    Thread Starter mhoney

    (@mhoney)

    yeah I saw that tutorial before, but as I was saying on my previous post, it was working before, this is not a new website, suddenly stopped and works for any other asset like videos so it’s not inactive on server either

    • This reply was modified 6 years, 1 month ago by mhoney.
    Plugin Author Emre Vona

    (@emrevona)

    this is your opinion. your site is served on Nginx server so you need yo add the rule manually: https://resmim.net/preview/rgR7G6.jpg

    Thread Starter mhoney

    (@mhoney)

    No, It’s not my opinion, I have been optimizing this website for the last 2 months, that’s why I’m saying it worked 2 weeks ago, the rules are already there, it also works for js, css, mp4, webm (this two I added because your plugin doesn’t include them)

    But I see you don’t want to look more deep, thanks anyway

    • This reply was modified 6 years, 1 month ago by mhoney.
    Plugin Author Emre Vona

    (@emrevona)

    but the browser caching rules for jpg already exist in htaccess.
    I have no idea.

    Thread Starter mhoney

    (@mhoney)

    me either that is why I was asking, I know pagespeed now changed the cache time again, but the other assets work perfectly, I don’t know what is the issue with pngs and jpgs

    Plugin Author Emre Vona

    (@emrevona)

    did you contact hosting provider?

    Thread Starter mhoney

    (@mhoney)

    I did, they say nothing changed, I wrote again about rechecking the directive on the nginx file, will let you know if they say anything, this thing is baffling me

    Plugin Author Emre Vona

    (@emrevona)

    ok. please let me know if there is browser caching rules in the /etc/nginx/nginx.conf or not.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Leverage Browsing Cache not working for images’ is closed to new replies.