Etag/Last Modified - the numpty question I've always wanted to know.

[Geebee]

(01-28-2011 03:12 PM)Thompson Wrote:  I've always heard (askapache.com) that for static content (JS/CSS), it's best to set far futures headers by setting *both* cache-control and expires headers. And then unsetting *both* etags and last modified.

Anybody have any thoughts on this?

The idea is that it is supposed to prevent any request at all for the file if the file is already in the browser cache.

This is exactly what we do, also for images and binaries (jpg, gif, pdf, odf, doc). But I don't have any info about if this is a better strategy than 1 'strong' (eg Expires) and 1 'weak' (eg Last Modified)... :-(.