ASP.NET修改Azure CDN Blob存储文件后缓存刷新问题求助

一、修复当前代码的属性设置逻辑 #

你当前的代码存在两个核心问题：一是仅在更新文件时设置缓存控制，新上传的文件会沿用CDN默认长缓存策略；二是上传操作可能重置Blob属性，导致缓存控制设置未生效。针对旧版Microsoft.WindowsAzure.Storage SDK，可调整代码如下：

public async Task<ImageInfoDto> UploadFilesAsync(string fileName, Stream fileStream, string contentType, bool isUpdated)
{
    try
    {
        var storageAccount = CloudStorageAccount.Parse(_configuration["StorageAccountConnectionString"]);
        var blobClient = storageAccount.CreateCloudBlobClient();
        var container = blobClient.GetContainerReference(_configuration["BlobStorageContainerName"]);
        var cdnEndpoint = _configuration["CdnEndpoint"];
        var blob = container.GetBlockBlobReference(fileName);

        // 先设置属性再上传，避免上传操作覆盖属性
        blob.Properties.ContentType = contentType;
        // 所有文件都配置缓存规则：更新时用短缓存，新文件用适中缓存
        blob.Properties.CacheControl = isUpdated ? "s-maxage=10, stale-while-revalidate=5" : "s-maxage=3600";

        fileStream.Position = 0;
        await blob.UploadFromStreamAsync(fileStream);

        return new ImageInfoDto
        {
            StorageUrl = blob.Uri.ToString(),
            CdnUrl = $"{cdnEndpoint}/{container.Name}/{fileName}",
            ContentType = contentType
        };
    }
    catch (Exception ex)
    {
        _logger.LogError(ex, "Failed to upload file");
        return null; // 补充返回值避免编译警告
    }
}

如果升级到推荐的新版Azure.Storage.Blobs SDK，代码会更简洁直观：

using Azure.Storage.Blobs;
using Azure.Storage.Blobs.Models;

public async Task<ImageInfoDto> UploadFilesAsync(string fileName, Stream fileStream, string contentType, bool isUpdated)
{
    try
    {
        var blobServiceClient = new BlobServiceClient(_configuration["StorageAccountConnectionString"]);
        var containerClient = blobServiceClient.GetBlobContainerClient(_configuration["BlobStorageContainerName"]);
        var blobClient = containerClient.GetBlobClient(fileName);
        var cdnEndpoint = _configuration["CdnEndpoint"];

        var uploadOptions = new BlobUploadOptions
        {
            HttpHeaders = new BlobHttpHeaders
            {
                ContentType = contentType,
                CacheControl = isUpdated ? "s-maxage=10, stale-while-revalidate=5" : "s-maxage=3600"
            }
        };

        fileStream.Position = 0;
        await blobClient.UploadAsync(fileStream, uploadOptions);

        return new ImageInfoDto
        {
            StorageUrl = blobClient.Uri.ToString(),
            CdnUrl = $"{cdnEndpoint}/{containerClient.Name}/{fileName}",
            ContentType = contentType
        };
    }
    catch (Exception ex)
    {
        _logger.LogError(ex, "Failed to upload file");
        return null;
    }
}

二、主动刷新CDN缓存（关键步骤） #

即使设置了短缓存规则，已存在于CDN节点的旧缓存不会立即失效。你需要在文件更新后，通过代码主动触发CDN刷新：

using Azure.ResourceManager.Cdn;
using Azure.ResourceManager.Cdn.Models;

public async Task RefreshCdnAsync(string cdnProfileName, string cdnEndpointName, string resourceGroupName, string filePath)
{
    var armClient = new ArmClient(new DefaultAzureCredential());
    var subscription = await armClient.GetDefaultSubscriptionAsync();
    var resourceGroup = await subscription.GetResourceGroupAsync(resourceGroupName);
    var cdnProfile = await resourceGroup.GetCdnProfileAsync(cdnProfileName);
    var cdnEndpoint = await cdnProfile.GetCdnEndpointAsync(cdnEndpointName);

    var refreshParams = new CdnEndpointContentParameters
    {
        ContentPaths = new List<string> { $"/{filePath}" } // 路径需与CDN访问路径完全匹配
    };

    await cdnEndpoint.RefreshContentAsync(WaitUntil.Completed, refreshParams);
}

在UploadFilesAsync方法完成文件更新后，调用此方法刷新对应CDN路径的缓存。

三、长期优化方案：内容版本化 #

从根源上避免缓存冲突，推荐使用内容哈希/版本号命名文件，例如{contentHash}.jpg。每次文件更新时生成新的哈希文件名，CDN会将其识别为全新资源，无需依赖缓存过期规则，同时可设置超长缓存时间提升性能。

四、验证缓存规则是否生效 #

可通过两种方式确认设置是否生效：

• 浏览器开发者工具的Network标签，查看CDN返回的Cache-Control响应头
• 使用命令行：curl -I {你的CDN文件URL}，检查输出中的Cache-Control字段

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