Hello!

On Fri, Jul 03, 2015 at 01:46:40PM +0200, Alexander Dreweke wrote:

> Hi
>
> webfonts are often distributed in various formats, so each platform can
> pick their preferred format[1].
>
> Currently mime-types for woff2, ttf and oft fonts are missing[2].
> Further the mime-type for html5 caching manifest is missing to[3].

We don't try to keep all possible extensions in our mime.types
file - rather, we list most popular file extensions there. If
needed, the list can be easily extended locally.

> [1]: https://github.com/choffmeister/roboto-fontface-bower/tree/develop/fonts
> [2]: http://www.iana.org/assignments/media-types/application/font-sfnt
> [3]: http://www.iana.org/assignments/media-types/text/cache-manifest
>
> Please find attached my patch for the default mime.types definitions.
>
> cu
> Alex

> diff --git c/conf/mime.types w/conf/mime.types
> index 89be9a4..a928b71 100644
> --- c/conf/mime.types
> +++ w/conf/mime.types
> @@ -14,6 +14,7 @@ types {
> text/vnd.sun.j2me.app-descriptor jad;
> text/vnd.wap.wml wml;
> text/x-component htc;
> + text/cache-manifest appcache manifest;

Both "appcache" and "manifest" extensions doesn't seem to be
defined by any standard (or at least convention). And the
"manifest" extension seems to be widely used for other things.

>
> image/png png;
> image/tiff tif tiff;
> @@ -25,6 +26,8 @@ types {
> image/webp webp;
>
> application/font-woff woff;
> + application/font-woff2 woff2;

As far as I understand, no MIME type yet registered for WOFF2, and
once registered, it's likely to be font/woff2, not
application/font-woff2, see current working draft at
http://www.w3.org/TR/WOFF2/.

> + application/font-sfnt ttf oft;

Not sure if we should add anything beyond woff (and woff2 once
registered).

> application/java-archive jar war ear;
> application/json json;
> application/mac-binhex40 hqx;

--
Maxim Dounin
http://nginx.org/

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel