Anonymous User 16850768
(@anonymized-16850768)
We’re happy to hear that you like the performance of the Cache Enabler plugin. Currently we have no plans to add a feature that allows browser caching. Instead, this can be done by setting the Cache-Control HTTP header to your desired specifications.
@coreyk
Browser caching is important for pagespeed. I don’t want to use any other plugin for this. This feature is available in all cache plugins. It is important. The omission of this feature is a shortcoming.
I added:
<filesMatch “.(ico|pdf|flv|jpg|svg|jpeg|png|gif|js|css|swf)$”>
Header set Cache-Control “max-age=604800, must-revalidate” “expr=%{REQUEST_URI} !~ m#^/wp-admin#”
</filesMatch>
But still pagespeed gives warning. “Serve static assets with an efficient cache policy”
I couldn’t solve the problem. 🙁
thanks.
-
This reply was modified 6 years, 6 months ago by
devrekli.
Anonymous User 16850768
(@anonymized-16850768)
Thank you for sharing your feedback, we sincerely appreciate it.
To serve your static assets with an efficient cache policy you’ll need to check the content type of the assets being reporting and ensure that your rule is being applied correctly. For example, the following snippet could be used on an Apache server in the .htaccess files to cache files that match .jpg, .jpeg, .png, .js, and .css for seven days:
<filesMatch ".(jpg|jpeg|png||js|css)$">
Header set Cache-Control "max-age=604800"
</filesMatch>