[PATCH] MIME: Added avif/avifs types.

[Ryo Hirafuji]

Thank you for reviewing, Dounin!

Yeah, I know that image/avif or image/avif-sequence are not registered in
IANA list yet,
but image/webp is also not registered in IANA list, isn't it?

WebP and AVIF are similar in some points.
They are both based on Royalty-free Video format, VP8 for WebP[1] and AV1
(based upon VP9) for AVIF[2].

AVIF is already supported in Windows[3], and it is planned to support in
Chrome[4] and Firefox[5] in the near future.

So I think it is worth to add "image/avif" to mime.types, if "image/webp"
is worth to be listed in mime.types.

Please tell your opinion!

[1] A new image format for the Web  |  WebP  |  Google Developers
https://developers.google.com/speed/webp/

[2] AV1 Image File Format (AVIF)
https://aomediacodec.github.io/av1-avif/

[3] AOMediaCodec/av1-avif Wiki
https://github.com/AOMediaCodec/av1-avif/wiki#demuxers--players

[4] 960620 - Support AVIF - An open-source project to help move the web
forward. - Monorail
https://bugs.chromium.org/p/chromium/issues/detail?id=960620

[5] 1443863 - (AVIF) Implement support for AV1 Still Image File Format
(AVIF)
https://bugzilla.mozilla.org/show_bug.cgi?id=1443863


2020年2月4日(火) 2:20 Maxim Dounin <mdounin at mdounin.ru>:

> Hello!
>
> On Mon, Feb 03, 2020 at 04:55:06PM +0900, 平藤燎 wrote:
>
> > Hello, I added new mime-types, "image/avif" and "image/avif-sequence".
> > Please take a look,
> >
> > # HG changeset patch
> > # User Ryo Hirafuji <ryo.hirafuji at link-u.co.jp>
> > # Date 1580715197 -32400
> > #      Mon Feb 03 16:33:17 2020 +0900
> > # Branch mime-avif-avifs
> > # Node ID 28c8371bb45be38623f8ac0e958d14b55600198a
> > # Parent  b8a512c6466c3b2f77876edf14061c5d97e6159f
> > MIME: Added avif/avifs types.
> >
> > "avif" is an image format based on AV1, royalty-free video coding format.
> > "avifs" is an image sequence format, that contains multiple avif images
> > like animated gifs.
> >
> > [Reference]
> > avif/avifs: https://aomediacodec.github.io/av1-avif/
> > AV1: https://aomediacodec.github.io/av1-spec/av1-spec.pdf
> >
> > diff -r b8a512c6466c -r 28c8371bb45b conf/mime.types
> > --- a/conf/mime.types Tue Jan 21 16:39:42 2020 +0300
> > +++ b/conf/mime.types Mon Feb 03 16:33:17 2020 +0900
> > @@ -20,6 +20,8 @@
> >      image/tiff                                       tif tiff;
> >      image/vnd.wap.wbmp                               wbmp;
> >      image/webp                                       webp;
> > +    image/avif                                       avif;
> > +    image/avif-sequence                              avifs;
> >      image/x-icon                                     ico;
> >      image/x-jng                                      jng;
> >      image/x-ms-bmp                                   bmp;
>
> Thank you for the patch.
>
> Note that nginx doesn't try to maintain all the mime types known,
> but rather tries to supply types generally needed for a web
> server.  Particular MIME types don't seem to be widely used,
> and not even registered by IANA[1].
>
> If you want to use these types in your configuration, consider
> modifying mime.types locally or extending the existing MIME types
> list using the "types" directive (http://nginx.org/r/types).
>
> [1] https://www.iana.org/assignments/media-types
>
> --
> Maxim Dounin
> http://mdounin.ru/
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20200204/9c1a54ba/attachment.htm>