Postman返回Cannot access a closed file，获取用户头像接口报错求助

在Postman中调用接口时返回：
Cannot access a closed File.

需求是实现添加头像时将文件存储在服务器wwwroot文件夹，路径存入数据库，同时返回头像，但接口始终报错，以下是获取头像的接口代码：

public async Task<IActionResult> GetProfilePicture([FromQuery] string userId)
{
    FileStreamResult file;
    if (userId == null)
        return BadRequest("Something went wrong");

    // 查找用户获取数据库中保存的头像路径
    var userPP = await _context.Users.FindAsync(userId);
    if (userPP == null)
        return BadRequest("Something went wrong! Try again");

    // 从路径中获取文件扩展名
    var ext = Path.GetExtension(userPP.ProfilePicture);

    string contentType;
    // 根据扩展名设置对应的Content-Type
    switch (ext)
    {
        case ".jpg":
        case ".jpeg":
            contentType = "image/jpeg";
            break;
        case ".png":
            contentType = "image/png";
            break;
        case ".gif":
            contentType = "image/gif";
            break;
        default:
            contentType = "application/octet-stream";
            break;
    }

    // 打开文件流获取图片
    using (var fs = new FileStream(userPP.ProfilePicture, FileMode.Open, FileAccess.Read))
    {
        file = File(fs, contentType);
        return Ok(file);
    }
}

问题原因 #

错误根源在于using语句块的使用。using会在代码块执行完毕后自动释放FileStream资源，但你在using块内创建FileStreamResult并返回时，流还未被ASP.NET Core读取就已经被关闭，后续框架尝试读取这个已关闭的流时就会抛出“无法访问已关闭的文件”的异常。

修复方案 #

方案1：移除using语句，让框架管理流生命周期 #

直接创建FileStream并返回，ASP.NET Core会在响应发送完成后自动释放流资源：

public async Task<IActionResult> GetProfilePicture([FromQuery] string userId)
{
    if (userId == null)
        return BadRequest("Something went wrong");

    var userPP = await _context.Users.FindAsync(userId);
    if (userPP == null)
        return BadRequest("Something went wrong! Try again");

    var ext = Path.GetExtension(userPP.ProfilePicture);

    string contentType;
    switch (ext)
    {
        case ".jpg":
        case ".jpeg":
            contentType = "image/jpeg";
            break;
        case ".png":
            contentType = "image/png";
            break;
        case ".gif":
            contentType = "image/gif";
            break;
        default:
            contentType = "application/octet-stream";
            break;
    }

    // 直接创建流，由框架负责释放资源
    var fs = new FileStream(userPP.ProfilePicture, FileMode.Open, FileAccess.Read);
    return File(fs, contentType);
}

方案2：读取到内存流后返回（适合小文件） #

将文件内容读取到内存流，避免长时间占用文件句柄：

public async Task<IActionResult> GetProfilePicture([FromQuery] string userId)
{
    if (userId == null)
        return BadRequest("Something went wrong");

    var userPP = await _context.Users.FindAsync(userId);
    if (userPP == null)
        return BadRequest("Something went wrong! Try again");

    var ext = Path.GetExtension(userPP.ProfilePicture);

    string contentType;
    switch (ext)
    {
        case ".jpg":
        case ".jpeg":
            contentType = "image/jpeg";
            break;
        case ".png":
            contentType = "image/png";
            break;
        case ".gif":
            contentType = "image/gif";
            break;
        default:
            contentType = "application/octet-stream";
            break;
    }

    using (var fs = new FileStream(userPP.ProfilePicture, FileMode.Open, FileAccess.Read))
    {
        var memoryStream = new MemoryStream();
        await fs.CopyToAsync(memoryStream);
        memoryStream.Position = 0; // 重置流指针到起始位置
        return File(memoryStream, contentType);
    }
}

方案3：使用PhysicalFile方法（最简洁） #

直接传入文件路径，让框架处理文件读取和资源释放：

public async Task<IActionResult> GetProfilePicture([FromQuery] string userId)
{
    if (userId == null)
        return BadRequest("Something went wrong");

    var userPP = await _context.Users.FindAsync(userId);
    if (userPP == null)
        return BadRequest("Something went wrong! Try again");

    var ext = Path.GetExtension(userPP.ProfilePicture);

    string contentType;
    switch (ext)
    {
        case ".jpg":
        case ".jpeg":
            contentType = "image/jpeg";
            break;
        case ".png":
            contentType = "image/png";
            break;
        case ".gif":
            contentType = "image/gif";
            break;
        default:
            contentType = "application/octet-stream";
            break;
    }

    // 直接传入文件路径，框架自动处理读取和资源释放
    return PhysicalFile(userPP.ProfilePicture, contentType);
}

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