Comments on: How to force an update of cached files, images, favicon

By: Jason Cross

Jason Cross — Thu, 15 Nov 2012 19:59:34 +0000

@alejandro, thanks for the tip!

By: Alejandro Cavallo

Alejandro Cavallo — Wed, 14 Nov 2012 00:55:40 +0000

Hey good tip, but if you add a parameter to the static file it won’t be cached at all, but this is not desirable for resources that are not changed frequently.
A better approach is to modify the file path (or name) by introducing a hash which will change when the file is modified; then in the apache configuration you can strip that value to get the right file path (or name). See here: https://developers.google.com/speed/docs/best-practices/caching?hl=es-419#LeverageBrowserCaching

By: Jason Cross

Jason Cross — Mon, 01 Oct 2012 18:52:53 +0000

Thanks, Rene. I sure did reference it incorrectly and the article is updated to reflect that.

By: René Thiel

René Thiel — Mon, 01 Oct 2012 16:23:12 +0000

That might be a nice workaround to the aggressive caching-behaviour (especially the favicons). However: technically speaking this solution doesn’t depend on a “tag”, it’s an additional URL-Parameter, more specific a GET-Parameter, but not a tag in the meaning of the word. The article is very good – nothing to add.

By: Kathy

Kathy — Mon, 17 Oct 2011 12:18:17 +0000

Thanks for the info.. great tip!

By: Bad web design repels people

Bad web design repels people — Wed, 06 Jul 2011 17:41:10 +0000

[...] This post was originally written for Immense Networks. [...]