Title: [Plugin: W3 Total Cache] Does W3TC write expires headers?
Last modified: August 20, 2016

---

# [Plugin: W3 Total Cache] Does W3TC write expires headers?

 *  Resolved [sadhaka](https://wordpress.org/support/users/sadhaka/)
 * (@sadhaka)
 * [13 years, 8 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/)
 * 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/](http://wordpress.org/extend/plugins/w3-total-cache/)

Viewing 15 replies - 1 through 15 (of 21 total)

1 [2](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/page/2/?output_format=md)

 *  Thread Starter [sadhaka](https://wordpress.org/support/users/sadhaka/)
 * (@sadhaka)
 * [13 years, 8 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3079993)
 * I should have mentioned that I’m not using a CDN. Any reason why YSLOW gives 
   me this message? I’ve enabled “Set expires header” for all options.
 *  Thread Starter [sadhaka](https://wordpress.org/support/users/sadhaka/)
 * (@sadhaka)
 * [13 years, 8 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080073)
 * Does anyone know anything about this – is it most likely a misreporting fault
   with “yslow” or is this a known W3TC issue?
 *  Thread Starter [sadhaka](https://wordpress.org/support/users/sadhaka/)
 * (@sadhaka)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080105)
 * Does anyone know whether W3TC is supposed to have this “expires headers” covered?
   I get the impression it should, but Page Speed and YSlow consistently complain
   about many “static components without a far-future expiration date”.
 * If I have this wrong and W3TC isn’t even supposed to enable this, or if it is
   and I therefore have a problem I’d love someone to explain it to me.
 *  [kletskater](https://wordpress.org/support/users/kletskater/)
 * (@kletskater)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080106)
 * Mail Fredrick himself, for he is not answering here at the forum
 *  Thread Starter [sadhaka](https://wordpress.org/support/users/sadhaka/)
 * (@sadhaka)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080107)
 * Well, it is a little disconcerting that Fredrick is the only person in the WordPress
   universe that seems able to offer any advice about this.
 * Does no-one apart from this author guru have *any* clue about this?
 * By the look of the support page, emails with questions are charged for. (Last
   resort, I’m afraid.)
 *  [mbrsolution](https://wordpress.org/support/users/mbrsolution/)
 * (@mbrsolution)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080108)
 * Hi [@sadhaka](https://wordpress.org/support/users/sadhaka/) are the static components
   related to your website or other websites?
 *  [Gans-S](https://wordpress.org/support/users/gans-s/)
 * (@gans-s)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080109)
 * I have the problem too. Components related to my website
 *  Thread Starter [sadhaka](https://wordpress.org/support/users/sadhaka/)
 * (@sadhaka)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080110)
 * [@mbrsolution](https://wordpress.org/support/users/mbrsolution/) – Hi – most 
   are related to my site – theme images, uploaded images for posts (many of these),
   but also some plugin css files; social widget files; even some minified w3tc 
   files. It looks to me like everything really.
 *  [mbrsolution](https://wordpress.org/support/users/mbrsolution/)
 * (@mbrsolution)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080111)
 * [@sadhaka](https://wordpress.org/support/users/sadhaka/), have a look at this
   link from this forum [http://wordpress.org/support/topic/w3-total-cache-isnt-working-at-all](http://wordpress.org/support/topic/w3-total-cache-isnt-working-at-all)
 * I hope this helps you.
 * Kind regards
 *  Thread Starter [sadhaka](https://wordpress.org/support/users/sadhaka/)
 * (@sadhaka)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080112)
 * [@mbrsolution](https://wordpress.org/support/users/mbrsolution/) – I took a look
   at that post, and from what I can understand, the gist of it was to check that
   the rewrite rules specified at the bottom of the “Install” section are indeed
   written to my .htaccess file, and they are.
 * My WP installation is (like many others), installed into a sub-folder from the
   site root. But the .htaccess at the site root contains all the code specified
   in the “Install” section.
 * I don’t have another .htaccess file in the WP sub-folder. Should I have?
 * So anyway, if I understand the main message of that post correctly, its recommendations
   don’t apply to my installation, and YSlow still gives me an ‘F’ for “Add expires
   headers”, complaining that “There are 36 static components without a far-future
   expiration date”, as before.
 *  [mbrsolution](https://wordpress.org/support/users/mbrsolution/)
 * (@mbrsolution)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080113)
 * Hi [@sadhaka](https://wordpress.org/support/users/sadhaka/), yes you should have
   another .htaccess in the sub folder. In my humble opinion every WordPress installation
   should have its own .htaccess even if it is in a sub-folder unless you are setting
   it up differently i.e you install your WordPress in a sub-folder but you place
   the .htaccess in the root and point it to a subfolder for security reasons.
 * However when you have 2 WordPress installed like I have one in the root and another
   in the sub-folder, they both have their own .htaccess file. One WordPress is 
   setup in English and the other is setup in Spanish.
 * I hope this helps you.
 * Kind regards
 *  Thread Starter [sadhaka](https://wordpress.org/support/users/sadhaka/)
 * (@sadhaka)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080114)
 * [@mbrsolution](https://wordpress.org/support/users/mbrsolution/) Thank you – 
   I must confess I don’t understand the rationale for having two .htaccess files
   which both do the same job, but I don’t know enough about it to judge, and perhaps
   indeed you are right.
 * But does this mean that both .htaccess files (the one in the site root and the
   other in the WordPress subdirectory) should contain the rewrite rules specified
   at the bottom of the “Install” section, as mentioned above (at least, the first
   block of code shown there that refers to the placing at site root)? That is, 
   should they be identical?
 * Many thanks.
 *  [mbrsolution](https://wordpress.org/support/users/mbrsolution/)
 * (@mbrsolution)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080115)
 * [@sadhaka](https://wordpress.org/support/users/sadhaka/), try and place the .
   htaccess file in your sub-directory where you have your WordPress installed and
   see what happens.
 * I am sure that your problem should be corrected and make sure that the .htaccess
   file is set to read your sub-directory and not your root directory.
 * Kind regards
 *  Thread Starter [sadhaka](https://wordpress.org/support/users/sadhaka/)
 * (@sadhaka)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080116)
 * But in W3TC’s “install” page, the server path that is specified in bold under“
   Rewrite rules” points to the root directory, not to the subdirectory.
 * I thought this was a reflection of the fact that in the WordPress “General Settings”
   my “WordPress Address (URL)” is set to the subdirectory (the “Site Address (URL)”
   being set to the domain root).
 * Minify works (I can see that in the source) and browser caching works – it’s 
   only the expires headers thing that doesn’t. How come they work if the .htaccess
   file is in the wrong place?
 * Confused.
 *  Thread Starter [sadhaka](https://wordpress.org/support/users/sadhaka/)
 * (@sadhaka)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/#post-3080117)
 * OK, I tried it – I copied the first .htaccess code that appears under “Rewrite
   rules” in W3TC’s “install” page and used it as a new .htaccess file in my installation’s
   subdirectory, cleared W3TC’s caches, ran YSlow again and exactly the same result:
   it reports “Grade F on Add Expires headers … There are 34 static components without
   a far-future expiration date”.
 * As far as I can see W3TC doesn’t do this expires headers thing, maybe at least
   for WordPress installations in subdirectories? But whatever I do, it simply does
   not do it.

Viewing 15 replies - 1 through 15 (of 21 total)

1 [2](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/page/2/?output_format=md)

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

 * ![](https://ps.w.org/w3-total-cache/assets/icon-256x256.png?rev=1041806)
 * [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/)

 * 21 replies
 * 4 participants
 * Last reply from: [sadhaka](https://wordpress.org/support/users/sadhaka/)
 * Last activity: [13 years, 5 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-does-w3tc-write-expires-headers/page/2/#post-3080123)
 * Status: resolved