cache expiration

Permalink
I'm not too familiar with cache expiration etc. Google tells me
"The following resources are missing a cache expiration. Resources that do not specify an expiration may not be cached by browsers..."
I gather there might be an easy way to do this with my .htaccess file? I am using APC, does that matter? How important is this for page load optimization?

Then let's say I set my expires for a far future date and then want to change my header image... how does that work? Would people who came before fail to see the change?

Thanks!

 
Mnkras replied on at Permalink Reply
Mnkras
can you please list the files, it depends on what/where they are.
nbruley replied on at Permalink Reply
Sure. (Fromhttp://gospelriver.com)
I think the main concerns might be the header image, the body image, navigation images (but only 2-3kb each) and general css? Maybe the google stuff from the site search if that were possible.

The following resources are missing a cache expiration. Resources that do not specify an expiration may not be cached by browsers:
main.css
typography.css
body.jpg
Welcome_nav2_on.jpg
mobile2.jpg
Fountain_Life_nav3.jpg
Messages_nav.jpg
music_nav2.jpg
music_cd_nav.jpg
play_nav2.jpg
audio_vid_nav.jpg
books_nav.jpg
bookmarks2_off.jpg
wall-hangings_off.jpg
Calendars.jpg
memorycd_nav.jpg
contact_nav.jpg
help_nav2.jpg
terms_of_use.jpg
resources.jpg
menubottom.jpg
right-edge.jpg
content.jpg
footer-back.jpg
footer-divider.jpg

The following cacheable resources have a short freshness lifetime:
counter.js
ga.js
shiny.css
cse_theme_shiny_form_bg.png
google_custom_search_watermark.gif

The following resources are explicitly non-cacheable. Consider making them cacheable if possible:
http://gospelriver.com/
ccm.base.css
jsapi
t.php
http://www.google.com
__utm.gif
http://www.google.com

Thanks again.