In order to display fonts right, browser must receive font files with correct http headers. If server does not set required headers, some browsers can report errors in console or completely fail to display fonts.
Probably, your server is already configured, and you don’t need to change anything. If not, you need to care about:
- Correct mime-type headers
- CORS headers – only if you serve fonts files & html pages from different domains
- For IE, check that your http headers for the font files do not have no-store or no-cache
(*) If you can’t set CORS headers, you can embed font files directly into CSS. Appropriate CSS file already exists in fontello archive.
Apache
To set right mime-types for font files, add this lines to config:
|
1 2 3 4 5 6 |
AddType application/x-font-ttf ttc ttf AddType application/x-font-otf otf AddType application/font-woff woff AddType application/font-woff2 woff2 AddType application/vnd.ms-fontobject eot |
If you can’t edit config, create .htaccess file in folder with your project and add lines there.
For CORS headers add:
|
1 2 3 4 |
<FilesMatch ".(eot|ttf|otf|woff|woff2)"> Header set Access-Control-Allow-Origin "*" </FilesMatch> |
nginx
By default nginx has no default mime types for fonts, and wrong mime type for .eot files. Go to folder with configs and find where mime types are defined. Usually, that’s in the mimes.types file.
- Search
.eotand string with it. - Add strings below.
|
1 2 3 4 5 6 |
application/x-font-ttf ttc ttf; application/x-font-otf otf; application/font-woff woff; application/font-woff2 woff2; application/vnd.ms-fontobject eot; |
For CORS headers, add something like this to your vhost config
|
1 2 3 |
location ~* \.(eot|otf|ttf|woff|woff2)$ { add_header Access-Control-Allow-Origin *; } |