Browser caching code added but no change?

  • Resolved Jeroen O.

    (@persuader69)


    3 years, 6 months ago

    To change the expiry time of browser caching we added the code to Nginx.
    But in the WP plugin settings we see no changes.
    How can we fix this?
    Thx

    The page I need help with: [log in to see the link]

Viewing 2 replies - 16 through 17 (of 17 total)
  • Thread Starter Jeroen O.

    (@persuader69)

    Hi,

    Thx for your reply.

    Here is the code as it is now.

    https://www.dropbox.com/s/dutcgxwsl2dqcwq/5uUKEYSvtW1S1J6UT8KcOjcbDVSuLjrQ.png?dl=0

    We should be able to fix this without Cloudflare.

    Let me know what else we can do?

    Thx,
    Jeroen

    Plugin Support Williams – WPMU DEV Support

    (@wpmudev-support8)

    Hi @persuader69

    The code looks fine but I’m afraid we really can’t do much more in this case. I see that currently most of JS/CSS assets and images have expiration time for browser caching set to 10 years (3650 days) and it’s perfectly fine to keep it like this.

    Browser caching is done by browser but it’s based on headers that webserver sends so it’s a server-side thing and a matter of server management. Hummingbird provides a “helper” feature to set that when allowed/possible but if there’s no CDN currently (such as CloudFlare) that could affect these settings, then it must be “something” in server configuration that prevents the changes.

    I’m afraid we’ve exhausted our options here and you would need to keep working with your host to make changes or (if they cannot or refuse to assist) go for a workaround using e.g. CloudFlare.

    Kind regards,
    Adam

Viewing 2 replies - 16 through 17 (of 17 total)
  • The topic ‘Browser caching code added but no change?’ is closed to new replies.