Hello!

On Mon, Mar 04, 2019 at 06:05:02AM +0100, Anas Bouzid wrote:

> # HG changeset patch
> # User Anas Bouzid <bouzid.anas.1@gmail.com>
> # Date 1551674425 -3600
> # Mon Mar 04 05:40:25 2019 +0100
> # Node ID 4424fc3aec3eb5de188de2f95adcbf095bf14816
> # Parent 3f1db95d758ab6b331065e99df47666bb1ed5e06
> MIME: add application/manifest+json type
>
> The .webmanifest extension should be served using
> the application/manifest+json MIME type.
> https://w3c.github.io/manifest/#media-type-registration
>
> diff -r 3f1db95d758a -r 4424fc3aec3e conf/mime.types
> --- a/conf/mime.types Sun Mar 03 16:49:02 2019 +0300
> +++ b/conf/mime.types Mon Mar 04 05:40:25 2019 +0100
> @@ -30,6 +30,7 @@
> application/java-archive jar war ear;
> application/json json;
> application/mac-binhex40 hqx;
> + application/manifest+json webmanifest;
> application/msword doc;
> application/pdf pdf;
> application/postscript ps eps ai;

Thanks for the patch.

For the record:

- The application/manifest+json is not something officially
registered (https://www.iana.org/assignments/media-types/media-types.xhtml).

- The specification does not seem to be complete, only a working
draft is available.

- The MIME type isn't present in Apache mime.types
(http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types).

Note that we generally only add most popular types to the
mime.types as shipped with nginx. It currently doesn't look like
the "application/manifest+json" type qualify.

Note that if you want to add additional types or serve some files
with specific custom types, you can do so using the "types"
directive, see http://nginx.org/r/types for examples.

--
Maxim Dounin
http://mdounin.ru/
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel