[Plugin: W3 Total Cache] Bad (Header) Caching-Control Values for combined/minified css files (4 posts)

  1. lautr
    Posted 6 years ago #

    Hello there,

    i just noticed that the CSS File wich is generated by W3TC has a really short Cache-Control Max Age (and must-revalidate), for example, thats what my regular css files look like:

    Cache-Control max-age=2592000, public

    thats what w3tc looks like, would be great if that would be configurable :)
    Cache-Control max-age=900, public, must-revalidate



  2. Frederick Townes
    Posted 6 years ago #

    If not using a CDN, the "Update external files every" field on the minify settings tab determines your expire time.

  3. lautr
    Posted 6 years ago #

    Indeed i'm not using a CDN and like i wrote 'Expires Header' works just fine (set to -> "Expires Fri, 22 Jan 2010 16:40:53 GMT") but the 'Cache-Control Header' is stick to -> 'Cache-Control max-age=900, public, must-revalidate'.

    'Maximum lifetime of cache objects' and 'Update external files every' is both set to 2678400.


  4. Frederick Townes
    Posted 6 years ago #

    Expires = current_time + life_time (in the config, default 86400)
    Max_age = expires - current_time (so each request this time decreases)

    Something else on your server is modifying headers for .css / .js files. This is not a known bug.

    If you want hands on support you can make a bug submission request using the support tab in the plugin.

Topic Closed

This topic has been closed to new replies.

About this Topic