Reading the plugin FAQ:
After you have enabled the plugin, look for the file "wp-content/cache/.htaccess". If it's not there you must create it. It should read:
# BEGIN supercache <IfModule mod_mime.c> <FilesMatch "\.html\.gz$"> ForceType text/html FileETag None </FilesMatch> AddEncoding gzip .gz AddType text/html .gz </IfModule> <IfModule mod_deflate.c> SetEnvIfNoCase Request_URI \.gz$ no-gzip </IfModule> <IfModule mod_headers.c> Header set Cache-Control 'max-age=3, must-revalidate' </IfModule> <IfModule mod_expires.c> ExpiresActive On ExpiresByType text/html A3 </IfModule> `` # END supercache
The Question is why
Header set Cache-Control 'max-age=3, must-revalidate'
must be 3 seconds?
Shouldn't this be much higher? Can i change this value to let's say 604800 ?
This is my own scenario:
- I dont allow comments
- I don't have dynamic widgets
- I post every day but i don't bother if my content is shown a few hours after
- I run an XML import every week - adding about 500 posts in one hour
Quote: Most users will not even notice the cache validation requests, but delivering outdated cache files is much more visible. - I am doing this more for SEO purposes - please look at: http://seobyg.com/http-header/cache-control
i think it does matter for SEO to have a high max-age - right ?