Our webdesigner has created a CSS with the following font-face:
@font-face {
font-family: \'oxygenregular\';
src: url(\'oxygen-regular-webfont.eot\')
I just had the same bug, and for those who want to have a pure solution (non exact-technology related): you need to make sure that the font headers you're sending are not saying no-cache. On top of what was written before, there are actually two headers which can do it:
"cache-control: no-cache"
and
"pragma: no-cache"
Both of those are saying browser the same, the first one is part of HTTP1.1, the second one is older (HTTP1.0).
Now, solutions:
"cache-control" to "max-age=0"; you can drop pragma header, it's obsolete (or set it to "pragma: cache").no-cache values, and set proper max-age (e.g. "cache-control: max-age=3600" - one hour cache). Pragma can be set to "pragma: cache" or removed completely.