As cc young said, in order to get rid of the Chrome warning "Resource interpreted as Font but transferred with MIME type application/font-woff" you need to use "application/x-font-woff"
–
JamieJan 2 '13 at 17:20

9

Chrome Version 24.0.1312.52 seems to still reply with the "Resource interpreted as Font but transferred..." if you use application/font-woff. Seems still need to use "application/x-font-woff" for now.
–
NicholiJan 16 '13 at 1:41

In Gecko, web fonts are subject to the same domain restriction (font files must be on the same domain as the page using them), unless HTTP access controls are used to relax this restriction.
Note: Because there are no defined MIME types for TrueType, OpenType, and WOFF fonts, the MIME type of the file specified is not considered.

@UmarFarooqKhawaja this answer is incomplete, but not wrong. The only thing that changed between this answer and your comment is application/font-woff was added to the standard, replacing such things as application/x-font-woff (actual software updating in practice is another matter). Nothing has made madey-uppey content-types of the form font/xxx valid.
–
Jon HannaAug 21 '14 at 9:15

'application/octet-stream' is the web server equivalent of saying "I don't know what this is".
–
SynchroApr 26 '12 at 15:02

1

Yes, I know. But the key point was that it worked whereas many of the more specific options didn't seem to result in the fonts being used over IIS7. My comment was more pragmatic than trying to be the most correct (because that wasn't working).
–
Michael KennedyApr 27 '12 at 15:17

That works by fooling chrome into thinking it's a different type of font than it actually is. According to Marcel "application/x-font-woff" is what you should be using right now. Thanks for your answer :)
–
Nico BurnsMar 8 '11 at 16:26

Mime type might not be your only problem. If the font file is hosted on S3 or other domain, you may additionally have the issue that Firefox will not load fonts from different domains. It's an easy fix with Apache, but in Nginx, I've read that you may need to encode your font files in base-64 and embed them directly in your font css file.

For all Solution index.php remove form url and woff file allowed. for write below code in .htaccess file and and make this alternation to your application/config/config.php file:
$config['index_page'] = '';

For only Linux hosting server..htaccess file details

AddType font/ttf .ttf
AddType font/eot .eot
AddType font/otf .otf
AddType font/woff .woff
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
#Removes access to the system folder by users.
#Additionally this will allow you to create a System.php controller,
#previously this would not have been possible.
#'system' can be replaced if you have renamed your system folder.
RewriteCond %{REQUEST_URI} ^system.*
RewriteRule ^(.*)$ /index.php?/$1 [L]
#When your application folder isn't in the system folder
#This snippet prevents user access to the application folder
#Submitted by: Fabdrol
#Rename 'application' to your applications folder name.
RewriteCond %{REQUEST_URI} ^application.*
RewriteRule ^(.*)$ /index.php?/$1 [L]
#Checks to see if the user is attempting to access a valid file,
#such as an image or css document, if this isn't true it sends the
#request to index.php
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?/$1 [L]
</IfModule>
<IfModule !mod_rewrite.c>
# If we don't have mod_rewrite installed, all 404's
# can be sent to index.php, and everything works as normal.
# Submitted by: ElliotHaughin
ErrorDocument 404 /index.php
</IfModule>