If you are getting warnings like Resource interpreted as Font but transferred with MIME type font/x-woff in Google Chrome then it means your web server is serving the font with the wrong MIME type.
It took awhile for the WOFF font format to get an approved MIME type so there are several variations hanging around.
Thank God an official type was finally decided on,
Unfortunately, Google Chrome (as of 26 beta) still expects you to use
application/x-font-woff and doesn’t recognize
application/font-woff as a valid MIME type. This has been fixed in the WebKit trunk but hasn’t been merged into Chrome yet. The Chromium bug report has been closed so it should be coming soon.
Until it is merged into a Chrome release you have a couple of options.
application/x-font-woffwhich will fix the Chrome warnings but isn’t the approved MIME type. You’ll need to change it again later.
application/font-woffwhich will continue to cause warnings in Chrome but is the approved MIME type. Obviously the warnings will go away once the WebKit fix has been merged into Chrome but this will take a few months to make it into a release.
Since the warnings are only annoying I would recommend switching to the approved MIME type right away. The warnings will resolve themselves in time.
The steps to fix this will vary by web server but for IIS Express this is how you’d do it.
Search for “.woff” and you’ll find a line like this:
<mimeMap fileExtension=".woff" mimeType="font/x-woff" />
Change mimeType to
<mimeMap fileExtension=".woff" mimeType="application/font-woff" />
Restart your IIS Express site.