Leverage caching

I'm running some post-launch tests on one of my sites using Google Insights and it's recommending using leverage caching. Is this feasible with a CMS, where the client most likely won't want to save time by caching files in order to increase page speed? Has anyone crossed this bridge?

View Replies:
Phallanx replied on at Permalink Reply
When Insights say "Leverage browser caching" it is referring to the server and not the CMS. What it means is that you have your server set up so that browsers (and intermediate proxy servers) do not effectively cache the content.
Here is the content of my servers' .htaccess that sets up the associated parameters.
(NOTE: the modules have to be enabled in Apache for them to take effect)

<IfModule mod_expires.c>
<IfModule mod_headers.c>
Header unset Pragma
FileETag None
Header unset ETag
# Turn on Expires and set default to 0
ExpiresActive On
ExpiresDefault A0
# Set up caching on media files for 1 year (forever?)
<FilesMatch "\.(flv|ico|pdf|avi|mov|ppt|doc|mp3|wmv|wav|gif|jpg|jpeg|png|swf)$">
ExpiresDefault A29030400
Header append Cache-Control "public"
# Set up 31 days caching on commonly updated files
<FilesMatch "\.(xml|txt|html|js|css)$">