@karelz I am looking at the API review process you linked above, which step did this issue reach? Step one is someone creating an issue (this issue), step two is for the team to assign an owner, why hasn’t that happened yet?

Here is my proposal for the common mime types that I believe should exist under the System.Net.Mime.MediaTypeNames namespace. I have checked the existing ones in the list below. I also went with the assumption that mime types of executable files will not be added, is that fair? Maybe not.

Proposal

System.Net.Mime.MediaTypeNames.Text

• Plan = “text/plain”
• Html = “text/html”
• Xml = “text/xml”
• RichText = “text/richtext”
• Csv = “text/csv”

System.Net.Mime.MediaTypeNames.Application

• Soap = “application/soap+xml”
• Octet = “application/octet-stream”
• Rtf = “application/rtf”
• Pdf = “application/pdf”
• Zip = “application/zip” // perhaps add all different kinds of non-executable MS mimetypes?
• Docx = “application/vnd.openxmlformats-officedocument.wordprocessingml.document”
• Xlsx = “application/vnd.openxmlformats-officedocument.spreadsheetml.sheet”
• Pdf = “application/pdf”
• Json = “application/json”
• JsonPatch = “application/json-patch+json”
• JsonLd = “application/ld+json”
• Xml = “application/xml”
• FormUrlencoded = “application/x-www-form-urlencoded”

System.Net.Mime.MediaTypeNames.Image

• Gif = “image/gif”
• Tiff = “image/tiff”
• Jpeg = “image/jpeg”
• Png = “image/png”
• Svg = “image/svg+xml”
• Webp = “image/webp”
• Bmp = “image/bmp”

Additional Categories

System.Net.Mime.MediaTypeNames.Multipart

• FormData = “multipart/form-data”
• Byteranges = “multipart/byteranges” // Use case: Send part of a document

System.Net.Mime.MediaTypeNames.Font

• Collection = “font/collection”
• Otf = “font/otf”
• Sfnt = “font/sfnt”
• Ttf = “font/ttf”
• Woff = “font/woff”
• Woff2 = “font/woff2”

System.Net.Mime.MediaTypeNames.Video

• Webm = “video/webm”
• Ogg = “video/ogg”
• Mp4 = “video/mp4”
• Mpeg = “video/mpeg”
• Mp2t = “video/mp2t”

System.Net.Mime.MediaTypeNames.Audio

• Midi = “audio/midi”
• Mp3 = “audio/mpeg”
• Webm = “audio/webm”
• Ogg = “audio/ogg”
• Wav = “audio/wav”

Sourced from IANA - Media Types with the help of Mozilla to pick some common mime types.

If I have missed anything that you believe is useful, add it in a comment.

https://github.com/dotnet/runtime/issues/1489#issuecomment-537625716

Triage: We are open to add a few of the MIME type enums. Next step: Create proposal with most used ones (with some links to usage ideally) and with names how they should be exposed.

@karelz I can agree that the audio, video, and office mime types have special uses and are not found in every application. But can we start with the file types used in the ASP.NET Core project templates, with the addition of related and some other well-known formats? I found most of the font and image formats there in the wwwroot directories.

Additional sources are: IANA Media Types and ASP.NET Core FileExtensionContentTypeProvider.

The Proposal

Application

• FormUrlEncoded = “application/x-www-form-urlencoded”
• Json = “application/json”
• JsonPatch = “application/json-patch+json”
• JsonSeq = “application/json-seq”
• Manifest = “application/manifest+json”
• Octet = “application/octet-stream”
• Pdf = “application/pdf”
• ProblemJson = “application/problem+json”
• ProblemXml = “application/problem+xml”
• Rtf = “application/rtf”
• Soap = “application/soap+xml”
• Wasm = “application/wasm”
• Xml = “application/xml”
• XmlDtd = “application/xml-dtd”
• XmlPatch = “application/xml-patch+xml”
• Zip = “application/zip”

Font

• Collection = “font/collection”
• Otf = “font/otf”
• Sfnt = “font/sfnt”
• Ttf = “font/ttf”
• Woff = “font/woff”
• Woff2 = “font/woff2”

Image

• Avif = “image/avif”
• Bmp = “image/bmp”
• Gif = “image/gif”
• Icon = “image/x-icon”
• Jpeg = “image/jpeg”
• Png = “image/png”
• Svg = “image/svg+xml”
• Tiff = “image/tiff”
• Webp = “image/webp”

Multipart

• ByteRanges = “multipart/byteranges”
• FormData = “multipart/form-data”

Text

• Css = “text/css”
• Csv = “text/csv”
• Html = “text/html”
• JavaScript = “text/javascript”
• Markdown = “text/markdown”
• Plain = “text/plain”
• RichText = “text/richtext”
• Rtf = “text/rtf”
• Xml = “text/xml”

Triage: The team discussed it on Thu 3/16. There was general agreement with the latest proposal - thank you @mmarinchenko! @wfurt will update the proposal into form ready for API review and mark it as such. We should be able to get it into 8.0 without any troubles.

With problemdetails, https://tools.ietf.org/html/rfc7807, implemented in .net core please add:

• application/problem+json
• application/problem+xml

The proposed list above seems quite reasonable. I can try to take it through API review @karelz. While I personally see the benefit small, the effort is also somewhat small and we get help from the community.

See dotnet/corefx#26201 for application/json and application/xml

I need text/csv )) Any plans?

Triage: We are open to add a few of the MIME type enums. Next step: Create proposal with most used ones (with some links to usage ideally) and with names how they should be exposed.

Please implement this already!

See this and this.

I was not planning to @AraHaan. Do you have example of public sites using it or is that something you applications do internally? https://www.rfc-editor.org/rfc/rfc6713 shows application/zlib and application/gzip so I’m note sure from where the -stream is coming. The mime type should be specific to the content not the implementation producing it, right?

It’s also missing the csv media type name as well.

This error has been open since 2017. It’s such a small thing to add these guys. When will PNG come?

Moreover, @Bilal-io’s list is no longer correct… See this for an updatet version.

text/json text/x-json text/javascript

I find it rather strange that the dotnet team are still insisting on collecting usage information… @oobayly

As long as the MIME type does not exist, you cannot increase the number of usage… Genius idea! 😂

I find it rather strange that the dotnet team are still insisting on collecting usage information in order to add something like image/png.

Unable to find any usage data for MIME types. However Mozilla have a list of Common MIME types.

@Bilal-io thanks for your proposal with names! Were you able to get some information about the usage of each of them? (as mentioned above - https://github.com/dotnet/runtime/issues/1489#issuecomment-541385535 https://github.com/dotnet/runtime/issues/1489#issuecomment-537625716) I have to admit some of these are not known to me. For some I would expect they are on decline these days (e.g. Midi?) … some usage data would make decisions here easier.

Regarding your question:

step two is for the team to assign an owner, why hasn’t that happened yet?

You are right that we deviate from the process a bit – unless the API is super-active, we consider the area owners to be the owners (though not assigned explicitly). In case of Networking area, it is the members of our Networking team (incl. myself). Once API is ready, we discuss proposals in our team meeting to get more thoughts before marking it ready for API review. Also note that in principal we try to not assign issues unless someone works on them actively (otherwise we would be back in place where people had hundred and more issues assigned to them – which made assignments useless). Hopefully that makes sense …

I’m currently dealing with file uploads. It would be great to have MIME types for Office documents (Word, Excel).