如何解决App Service中AspCore3.0 Web应用JSON MIME类型不识别问题

Hey there, let's work through this JSON MIME type problem you're hitting with your ASP.NET Core 3.0 app deployed to Azure App Service. I've dealt with similar quirks before, so here are a few reliable solutions depending on your specific scenario:

1. Configure Static File MIME Types in Startup.cs #

If the issue is with static JSON files (like config files or static data files being accessed directly), the ASP.NET Core static files middleware might not be mapping .json to the correct MIME type by default (or the mapping got overridden). Update your Configure method to explicitly set this:

public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
    // Keep your existing middleware (like app.UseRouting(), app.UseAuthorization(), etc.)
    
    // Create a custom content type provider
    var contentTypeProvider = new FileExtensionContentTypeProvider();
    
    // Add or override the JSON MIME type mapping
    if (!contentTypeProvider.Mappings.ContainsKey(".json"))
    {
        contentTypeProvider.Mappings[".json"] = "application/json";
    }
    else
    {
        contentTypeProvider.Mappings[".json"] = "application/json"; // Override if existing entry is incorrect
    }
    
    // Use static files with the custom provider
    app.UseStaticFiles(new StaticFileOptions
    {
        ContentTypeProvider = contentTypeProvider
    });
    
    // Rest of your middleware setup (like app.UseEndpoints(...))
}

This ensures that any static .json files served through the ASP.NET Core pipeline will have the correct Content-Type: application/json header.

2. Set MIME Types via Azure App Service Configuration or web.config #

If your app is relying on IIS (Azure App Service uses IIS under the hood for ASP.NET Core apps) to handle static files directly, you might need to configure the MIME type at the IIS level:

Option A: Azure Portal #

• Go to your App Service in the Azure Portal
• Navigate to Configuration > Application Settings
• Scroll down to the MIME types section
• Add a new entry:
  • Extension: .json
  • MIME type: application/json
• Save the changes and restart your app

Option B: Manual web.config #

If you prefer to include this in your deployment package, add or update the web.config file in your project root:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <system.webServer>
    <staticContent>
      <!-- Remove any existing conflicting .json mapping first -->
      <remove fileExtension=".json" />
      <!-- Add the correct MIME type mapping -->
      <mimeMap fileExtension=".json" mimeType="application/json" />
    </staticContent>
    <!-- Keep other existing web.config settings (like aspNetCore module config) -->
  </system.webServer>
</configuration>

This forces IIS to serve .json files with the correct MIME type, bypassing any default ASP.NET Core middleware if needed.

3. Ensure API Endpoints Return Correct Content-Type #

If the problem is with API responses not being recognized as JSON, double-check that your JSON formatter is configured properly. In ASP.NET Core 3.0, the default JSON serializer should return application/json, but sometimes custom configurations can break this. Update your ConfigureServices method to explicitly set the content type:

public void ConfigureServices(IServiceCollection services)
{
    services.AddControllers()
        .AddJsonOptions(options =>
        {
            // Explicitly set the content type for JSON responses
            options.JsonSerializerOptions.ContentType = System.Net.Mime.MediaTypeNames.Application.Json;
        });
    
    // Other service configurations
}

This guarantees that all your API endpoints return responses with the correct Content-Type header.

Start by figuring out whether the issue is with static JSON files or API responses, then pick the corresponding fix. Most of the time, either the static file middleware config or App Service MIME type setting will resolve the problem.

内容的提问来源于stack exchange，提问作者Julien