I noticed some strange extensions and now I am pretty sure they were automatically parsed from rfc, but since it is not structured errors sometimes occur
This document specifies syntax and semantics for the storage of [AV1] images in the generic image file format [HEIF], which is based on [ISOBMFF]. While [HEIF] defines general requirements, this document also specifies additional constraints to ensure higher interoperability between writers and readers when [HEIF] is used with [AV1] images.
So image/avif can have .heifs extension, but it is better to return image/heif-sequence type for .heifs
I noticed some strange extensions and now I am pretty sure they were automatically parsed from rfc, but since it is not structured errors sometimes occur
image/heic: subtype, for
I think this 2 extensions we parsed automatically from rfc https://www.iana.org/assignments/media-types/image/heic
.for can be an extension for "text/x-fortran" according to sources/from-apache
application/vnd.wfa.dpp: NA
Same for application/vnd.wfa.dpp
https://www.iana.org/assignments/media-types/application/vnd.wfa.dpp
image/avif: or
image/avif does not have extension "or"
https://www.iana.org/assignments/media-types/image/avif
application/vnd.etsi.asic-e+zip: or
and in
https://www.iana.org/assignments/media-types/application/vnd.etsi.asic-e+zip
vnd.exstream-package: or
https://www.iana.org/assignments/media-types/application/vnd.exstream-package
audio/atrac-advanced-lossless: and
https://www.iana.org/assignments/media-types/audio/ATRAC-ADVANCED-LOSSLESS
image/heif-sequence is better for .heifs
As i got it avif is a subtype of heif - https://aomediacodec.github.io/av1-avif/
So image/avif can have .heifs extension, but it is better to return image/heif-sequence type for .heifs