Asp.Net Core 2.0 Web应用自定义扩展名静态文件返回404求助

Hey there, I’ve run into this exact issue before—ASP.NET Core’s static file middleware doesn’t automatically handle custom file extensions out of the box, which is why your .static_json.json works (.json is a default supported extension) but your custom ones throw a 404. Let’s fix this step by step.

Why This Happens #

By default, the static file middleware only recognizes a predefined list of common file extensions (like .html, .css, .js, .json). Any extension not on that list gets rejected with a 404, even if the file exists in the correct folder.

Solution 1: Allow Specific Custom Extensions (Recommended) #

The safest way is to explicitly map your custom extension to a MIME type using FileExtensionContentTypeProvider. Here’s how to set this up in your Startup.cs:

1. Open your Startup.cs file and locate the Configure method.
2. Add the following code to configure the static file middleware with your custom extension mapping:

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
    // Initialize the content type provider
    var contentTypeProvider = new FileExtensionContentTypeProvider();
    
    // Add your custom extension and its corresponding MIME type
    // Replace ".your-custom-ext" with your actual extension, and set the correct MIME type
    // Example: if it's a text file, use "text/plain"; if it's a binary file, use "application/octet-stream"
    contentTypeProvider.Mappings[".your-custom-ext"] = "application/octet-stream";

    // Use static files with the configured provider
    app.UseStaticFiles(new StaticFileOptions
    {
        ContentTypeProvider = contentTypeProvider
    });

    // Keep your existing middleware configurations (like app.UseMvc() etc.) below
}

Solution 2: Allow All Unknown File Types (Not Recommended) #

If you need to support any arbitrary extension (note: this poses a security risk, as it could expose sensitive files on your server), you can enable serving unknown file types:

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
    app.UseStaticFiles(new StaticFileOptions
    {
        ServeUnknownFileTypes = true,
        DefaultContentType = "application/octet-stream" // Default MIME type for unknown files
    });

    // Your other middleware setup here
}

⚠️ Important Security Note: Only use this option if you fully trust the files in your static content directory—this can allow access to files like .config or .db if they’re present, which is a big no-no for production.

Quick Checks to Verify #

• Double-check that your custom extension file is in the correct static content folder (default is wwwroot; if you’re using a different folder, make sure you’ve configured the FileProvider in StaticFileOptions).
• Ensure the URL you’re using matches the file path exactly (e.g., if your file is wwwroot/docs/report.custom, the URL should be http://your-domain/docs/report.custom).
• Confirm no other middleware (like routing or authorization) is intercepting the request before it reaches the static file middleware.

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