May 29, 2011
“Resource interpreted as Font but transferred with MIME type …”
Have you seen a warning like this in your web browser console?
“
Resource interpreted as Font but transferred with MIME type ...
“
Some browsers, like Google Chrome, will show this warning when a font is downloaded from a web server that sets an unexpected MIME type for fonts.
For many font types, there is a solution!
Update the configuration for your web server with the following MIME type per font file extension:
- .ttf — font/truetype
- .otf — font/opentype
- .eot — application/vnd.ms-fontobject
- .woff — application/x-font-woff
If you are using Apache configuration, you may include the AddType directive for each font type:
AddType application/vnd.ms-fontobject eot
AddType font/opentype otf
AddType font/truetype ttf
AddType application/x-font-woff woff
With a specific MIME type configured per font, and not the generic application/octet-stream
MIME type, you should no longer see a warning in your web browser console.
This configuration — while effective for cleaning up your console — does not include the technically correct MIME type for fonts like OTF, TTF, and WOFF. For these font types, an official MIME type has not (yet) been approved. An official type for WOFF — application/font-woff — has been requested.
Pingback: Michael Sharman - chapter31 » Setting font MIME types in apache()
Pingback: Google Chrome gives warning Resource interpreted as Font but transferred with MIME type application/octet-stream: | Ngoding()