Super .htaccess file

[eluser]Philip Ramirez[/eluser]
[quote author="sdbruder" date="1217070074"]clearing the browser cache will do it, *for your client*.

We use aggressive caching with ExpiresDefault "access plus 1 year", but to circumvent that same agressive caching we use a global 'serial number' in all urls that mention cacheable files (images, js, css, etcetera), and part of our build process (Makefile) auto-updates it when some of that files changed, so /img/somefile.127.jpg got changed to /img/somefile.128.jpg in all generated html, and that some rewrite rules as

RewriteRule (.*)\.[0-9]+\.js $1.js
RewriteRule (.*)\.[0-9]+\.css $1.css
RewriteRule (.*)\.[0-9]+\.html $1.html

permits that none of our files need to be renamed.[/quote]

Using something like main.css?v=123456560823 also handles that problem.

EDIT: apparently using query strings only works with IE and FF. So, sdbruder's way is def. the safest way!