ewwatson - 1:15 pm on Nov 13, 2012 (gmt 0)
OK here is what I ended up with. After reading for weeks on this I think this is the best setup. The only thing it seems I went out on a limb on is caching html for a long time. I toyed with this in my brain. Many say cache css for a long time. Well I can't cache css, or js for that matter, without caching the html. When ever I edit one 9 times out of 10 I'm editing one of the others. Well if one is a new copy and one isn't the user will very likely see something wonky or unstyled, or un-js'ed.
My question is this? Am I missing something about caching the html? Or is the only downside the user waits 90 days to see the updated copy? Additionally Google always sees the newset copy correct? Thanks for your knowledge!
# Compress Files
# Turn off the ETags
Header unset ETag
# Cache Files 90 Days
ExpiresDefault "access plus 90 days"
Header append Cache-Control "public"