MVC 5如何强制浏览器打开PDF文件？求ActionResult类实现方案

Great job getting the PDF inline preview working with the traditional Response approach! It’s totally valid, but as you’re asking, there are cleaner ways to achieve this using MVC’s built-in ActionResult system that align better with the framework’s design. Let’s break down a couple of options:

Option 1: Modify the FileResult headers directly (no custom classes needed) #

Instead of manually writing to the Response stream, you can just adjust the Content-Disposition header before returning the existing FileStreamResult. This keeps everything within the MVC action pattern:

public ActionResult DownloadReport(string fileName)
{
    if (StaticData.ReportsTemp.TryGetValue(fileName, out var fileObj) && fileObj is FileStreamResult streamResult)
    {
        StaticData.ReportsTemp.Remove(fileName);
        
        // Critical: Reset the stream position to 0 (it might have been read during storage)
        streamResult.FileStream.Position = 0;

        if (streamResult.ContentType == System.Net.Mime.MediaTypeNames.Application.Pdf)
        {
            // Tell the browser to display the PDF inline
            Response.AddHeader("Content-Disposition", $"inline; filename=\"{streamResult.FileDownloadName}\"");
        }
        else
        {
            // For other files, explicitly trigger download (this is the default, but explicit is clearer)
            Response.AddHeader("Content-Disposition", $"attachment; filename=\"{streamResult.FileDownloadName}\"");
        }

        return streamResult;
    }

    return NotFound(); // Handle missing files gracefully
}

Option 2: Create a custom InlineFileResult for reusability #

If you need this inline behavior across multiple actions, a custom ActionResult keeps your code DRY:

public class InlineFileStreamResult : FileStreamResult
{
    public InlineFileStreamResult(Stream fileStream, string contentType) 
        : base(fileStream, contentType) { }

    protected override void WriteFile(HttpResponseBase response)
    {
        // Set the inline disposition header automatically
        response.Headers.Add("Content-Disposition", $"inline; filename=\"{FileDownloadName}\"");
        base.WriteFile(response);
    }
}

Then use it in your action like this:

public ActionResult DownloadReport(string fileName)
{
    if (StaticData.ReportsTemp.TryGetValue(fileName, out var fileObj) && fileObj is FileStreamResult streamResult)
    {
        StaticData.ReportsTemp.Remove(fileName);
        streamResult.FileStream.Position = 0;

        if (streamResult.ContentType == System.Net.Mime.MediaTypeNames.Application.Pdf)
        {
            return new InlineFileStreamResult(streamResult.FileStream, streamResult.ContentType)
            {
                FileDownloadName = streamResult.FileDownloadName
            };
        }

        return streamResult; // Defaults to attachment for non-PDF files
    }

    return NotFound();
}

Why this is better than the traditional Response approach #

• Follows MVC conventions: ActionResult is designed to encapsulate HTTP response logic, so using it keeps your code aligned with how MVC is intended to work.
• Testability: Custom ActionResults can be easily mocked or tested without needing a full HTTP context.
• Cleaner code: Avoids low-level stream writing and header manipulation directly in your action.

Your existing JS code doesn’t need any changes—window.open will still work perfectly with these implementations, as the browser will respect the Content-Disposition header we set.

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