u6gnhq
Last Updated: February 25, 2016
·
5.316K
· danosphere

Apache MIME type fix for .WOFF fonts in Chrome

Recently while working on a web app hosted on Apache and utilizing the Google Fonts API I was seeing a lot of errors that looked like this in the Chrome console:

Resource interpreted as Font but transferred with MIME type font/woff

After some quick googling it appeared all that needed to be done was to add the MIME type to http.conf or the appropriate .htaccess file. Depending on what you read, you'll find the definition for WOFF is still hazy:

Some say: http://stackoverflow.com/questions/4051826/font-face-problem-in-chrome

AddType application/x-font-woff .woff

W3 Says: http://www.w3.org/TR/WOFF/#appendix-b

AddType application/font-woff .woff

The above 2 variants still produced spurious results in Chrome, sometimes the font error would be appear, sometimes it would not (production branch of Chrome fyi). I ended up sticking with the w3 standard in the hopes a future chrome update would solve the problem now that the MIME type follows the w3 spec.

Say Thanks
Respond

1 Response
Add your response

9788
00f3cfa8388dfc9655e5887ffde9cfcc

This warning is gone on Chrome 30

over 1 year ago ·