I saw that Igor posted a link to the blog post below [1] in reference to another thread. That made me think - and I haven't looked, maybe we're already doing something like this. But, what if we calculated the MD5 for resources and appended that to the URL that we generate? That way, we can automatically set a long expires header, but since the URL would change if the resource changes, then we automatically handle this. It seems like something that would be broadly beneficial.
Thoughts? [1] - http://techblog.molindo.at/2008/08/wicket-interface-speed-up-caching-resources-forever.html -- Jeremy Thomerson http://www.wickettraining.com
