Adding a new MIME Type: Incorrect WOFF Fonts response header

WebbedIT

Verified User
Joined
Jun 10, 2012
Messages
15
Hi all.

Take a look at the following website in Chrome and you will see in the console two warnings saying "Resource interpreted as font but transferred with MIME type text/html ...":
http://www.firstaidneas.co.uk

When I then use Chromes Network and right click on either of the woff files to view the response headers I can see the server is responding to the client with:
Code:
HTTP/1.1 200 OK
Date: Sun, 10 Jun 2012 10:47:06 GMT
Server: Apache/2
X-Powered-By: PHP/5.2.17
Last-Modified: Tue, 6 Mar 2012 22:53:32 GMT
Expires: Mon, 11 Jun 2012 10:47:06 GMT
Cache-Control: public, max-age=86400
Vary: Accept-Encoding,User-Agent
Content-Encoding: gzip
Content-Length: 24820
Keep-Alive: timeout=1, max=98
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8

I need it to respond with /application/x-font-woff to get rid of these warnings. I have tried placing the following in the domains .htaccess file and in the servers /etc/httpd/conf/httpd.conf file:
Code:
AddType application/x-font-woff woff

I have also tried adding the following to /etc/httpd/conf/mime.types:
Code:
application/x-font-woff                         woff

I've restarted the http service after any changes but I am still getting this error.

Anyone got any advice on how I get the server to return the correct response?

Thanks,

Paul.
 
Back
Top