You can try to add to the the following to either .htaccess
AddType application/octet-stream otf
This should make the Save
Fonts does not have defined MIME types yet, but you could replace the above with
AddType font/otf otf
for a more informative MIME type. This should result in similar behaviour as with the application/octet-stream
The reason you get type Content-Type: text/plain
is because this is the default MIME type in apache (DefaultType text/plain
directive in http.conf
). So if the .otf file contains text then it will be rendered by the browser. But .otf files (Opentype Font Format) is supposed to be in a binary format so this is strange.
As for the client side (firefox):
When you click a link to download a file, the MIME type determines what action is taken. If you see an "Opening <filename>" dialog asking if you want to save the file or open it with a specified application, that normally means that no plugin is installed and enabled that can handle that MIME type and you have not previously selected a download action or helper application to always use for that type of file. Starting in Firefox 3 and SeaMonkey 2, the "Opening <filename>" dialog will also appear if you have selected "Always ask" as the action for the file's content type in your (Helper) Applications options/preferences (see below).