Font-awesome: Add cache buster to font URLs?

[kidplug]

Could you possibly add a cache buster URL param onto the font URLs, to avoid browser caching of the old font file during upgrades?

eg (note the v=3):
url('../font/fontawesome-webfont.woff?v=3')

[davegandy]

Ooooh. Great idea.

[kidplug]

Thanks! Chrome REALLY didnt want to pull the new font for me when i upgraded server side to v 3.0.0.
F5, reload, close tab, new tab - nothing worked. Had to restart Chrome, and I cant expect my users to do the same when I roll this out to PROD.

Thanks!

[davegandy]

Included in 3.0.1.

[exabrial]

Just wanted to point out, in the 3.0.2 release you forgot to update the URLs in to v3.0.2. They still say ?v=3.0.1 in the 3.0.2 release

[davegandy]

That's because the font files themselves didn't change. Just the CSS.

Sent from my iPhone

On Feb 12, 2013, at 11:42 AM, "Jonathan S. Fisher" [email protected] wrote:

Just wanted to point out, in the 3.0.2 release you forgot to update the URLs in to v3.0.2. They still say ?v=3.0.1 in the 3.0.2 release

—
Reply to this email directly or view it on GitHub.

[jukkasi]

Because versioning is using query strings it is impossible to get fontawesome files to get added to HTML5 application cache and ugly workaround is needed

http://stackoverflow.com/questions/24055244/webfont-font-awesome-not-working-corrently-offline

I think the version should be in the file names itself which is the recommended way to do versioning

http://www.stevesouders.com/blog/2008/08/23/revving-filenames-dont-use-querystring/

[tagliala]

@jukkasi please post your comment here #3286