Review FileExtensionContentTypeProvider and document the criteria for being included

[aspnet-hello]

From @Tratcher on Wednesday, April 27, 2016 11:44:38 AM

FileExtensionContentTypeProvider contains the file extension to content-type mappings used by the StaticFilesMiddleware. Only extensions listed will be served by default. The original list was copied from IIS but we've made some additions.

• Review the APIs and make sure it's easy enough for people to add and remove entries.
• Document the criteria for including an entry in the default list.
• Review the current entries to make sure they meet the criteria.

@DamianEdwards

Copied from original issue: aspnet/StaticFiles#129

[aspnet-hello]

From @DamianEdwards on Wednesday, April 27, 2016 7:49:16 PM

As part of the first item, I'd like to see what it would like to have an app set up to read a config file that specifies the file extension to content-type mappings, as an example.

[aspnet-hello]

From @muratg on Wednesday, May 25, 2016 11:55:39 PM

Moving to post RTM for now. Ping me if you think this has to be done this week.

[aspnet-hello]

From @Tragetaschen on Monday, July 11, 2016 2:57:25 AM

I've just tried to add a new file extension + content type to use with the file server.
There is definitely room for improvement:

var fileExtensionContentTypeProvider = new FileExtensionContentTypeProvider();
fileExtensionContentTypeProvider.Mappings[".vtt"] = "text/vtt";
var options = new FileServerOptions();
options.StaticFileOptions.ContentTypeProvider = fileExtensionContentTypeProvider;

app.UseFileServer(options);

[aspnet-hello]

From @Tratcher on Tuesday, September 13, 2016 4:32:34 PM

Policy considerations:

• Include file types included in other server's default sets
• Do not include file types likely to contain server-side code or configuration (e.g. cs, cshtml, json, etc..)
• Prefer mime types with well documented standards (e.g. RFCs)

This policy should be placed in the wiki and/or in a doc comment on FileExtensionContentTypeProvider

[aspnet-hello]

From @Tratcher on Wednesday, October 12, 2016 3:30:46 PM

Adding/Removing file types has discoverability issues, but we haven't found a fix without breaking changes. Consider removing the IContentTypeProvider abstraction, it's rarely replaced.

[aspnet-hello]

From @Tratcher on Tuesday, October 25, 2016 3:38:37 PM

@muratg recommend moving this to the 2.0 milestone for API breaking changes

[aspnet-hello]

From @muratg on Wednesday, June 14, 2017 3:35:51 PM

@DamianEdwards @glennc Do we want to do this in 2.0.0? (We may need to as it could be a breaking change.) If so, priority?

[aspnet-hello]

From @muratg on Tuesday, September 26, 2017 3:36:05 PM

@Tratcher Backlogging this for now.

[Tratcher]

@shirhatti @muratg

[muratg]

Good find! @shirhatti Let's close on this.