• Resolved sadhaka

    (@sadhaka)


    If I run ‘yslow’ on my blog (with W3TC installed) it tells me that I should add expires headers (gives me a Grade F because they’re not there – “There are 40 static components without a far-future expiration date.”).

    But doesn’t W3TC take care of all that? Perhaps it doesn’t. Sorry if I have that all wrong.

    http://wordpress.org/extend/plugins/w3-total-cache/

Viewing 6 replies - 16 through 21 (of 21 total)
  • This is the result of webserver configuration (modules etc…) I think. I have good .htaccess and xx3 static components without a far-future expiration date too

    Thread Starter sadhaka

    (@sadhaka)

    @gans-s Aha – so it may be a deficiency with the server configuration I’m using? Something not installed? What would be the absent culprit for this problem?

    @sadhaka can you find out if your host provider offers mod_expires on shared hosting?

    Thread Starter sadhaka

    (@sadhaka)

    I discover that mod_expires isn’t supported on my shared server. So that’s the reason that ‘expires headers’ isn’t working I guess?

    @sadhaka, yes that is correct. If mod_expires is not supported then you can not set this option using this plugin.

    Unfortunately your sever has this limitation that the plugin cannot control…..

    Could you close this ticket even though it is not resolved if you don’t mind.

    Kind regards

    Thread Starter sadhaka

    (@sadhaka)

    Well thanks for the insight.

Viewing 6 replies - 16 through 21 (of 21 total)

The topic ‘[Plugin: W3 Total Cache] Does W3TC write expires headers?’ is closed to new replies.