Basic UTF-8 encoded html pages served through UseStaticFiles don't have their ContentType charset correctly set #4546
Description
Description
When serving static utf-8 encoded html pages with Asp.Net Core's UseStaticFiles, the response ContentType is set to text/html and not text/html; charset=utf-8
To Reproduce
Steps to reproduce the behavior:
- Using ASP.NET Core v2.1.0, create a new Web API project, and disable IIS integration.
- Add
.UseDefaultFiles().UseStaticFiles()toStartup.Configure() - Create an html page named default.html in wwwroot and containing the following html fragment:
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<title>My page title</title>
</head>
<!--Some static content-->
</html>
- Run the project and use postman or equivalent to GET the default url
http://localhost:61106/ - Check the response header. It shows
Content-Type →text/html
Expected behavior
Content-Type should be text/html; charset=utf-8 (or whatever charset is declared in the html page).