如何避免从Microsoft Graph批量提取Teams图片时的速率限制问题

针对你遇到的Teams图片访问触发429限流的问题，以下是几个更有效的优化方案：

1. 遵循Graph返回的Retry-After头部进行重试 #

微软Graph的429响应会携带Retry-After字段，明确告知需要等待的秒数，硬编码固定间隔的重试策略无法适配动态限流规则。你应该优先读取该字段的值来确定等待时长：

public async Task<string> GetImageAsBase64(ILogger<TeamsHostedService> logger, string url, int retryCount = 3)
{
    AuthenticationHelper helper = new AuthenticationHelper(logger);
    var token = await helper.GetTokenForAppAsync();

    using (var httpClient = new HttpClient())
    {
        httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", token);
        
        for (int i = 0; i < retryCount; i++)
        {
            try
            {
                var imageBytes = await httpClient.GetByteArrayAsync(url);
                return Convert.ToBase64String(imageBytes);
            }
            catch (HttpRequestException ex) when ((int)ex.StatusCode == 429)
            {
                var waitTime = TimeSpan.FromSeconds(90);
                if (ex.Response?.Headers.RetryAfter != null)
                {
                    waitTime = ex.Response.Headers.RetryAfter.Delta ?? TimeSpan.FromSeconds(60);
                }
                logger.LogWarning("触发429限流，等待{WaitTime}后进行第{RetryNumber}次重试", waitTime, i+1);
                await Task.Delay(waitTime);
            }
            catch (Exception ex)
            {
                logger.LogError("获取图片Base64失败：URL={0} | 异常类型={1} | 消息={2}", url, ex.GetType(), ex.Message);
                if (i == retryCount - 1) return "";
                await Task.Delay(TimeSpan.FromSeconds(30));
            }
        }
        return "";
    }
}

2. 复用HttpClient实例 #

每次调用都创建新的HttpClient会导致TCP连接资源浪费，甚至加剧限流触发概率。建议通过依赖注入复用HttpClient实例：

// 在Program.cs中注册单例HttpClient
services.AddHttpClient<TeamsHostedService>();

// 在服务中注入
private readonly HttpClient _httpClient;
private readonly ILogger<TeamsHostedService> _logger;

public TeamsHostedService(HttpClient httpClient, ILogger<TeamsHostedService> logger)
{
    _httpClient = httpClient;
    _logger = logger;
}

// 修改GetImageAsBase64方法，移除内部HttpClient实例化
public async Task<string> GetImageAsBase64(string url, int retryCount = 3)
{
    AuthenticationHelper helper = new AuthenticationHelper(_logger);
    var token = await helper.GetTokenForAppAsync();
    
    _httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", token);
    // 后续重试逻辑同上
}

3. 实现图片缓存策略 #

Teams图片URL不会频繁变更，可将获取到的Base64结果缓存，避免重复请求Graph API：

private readonly IMemoryCache _cache;

// 构造函数注入IMemoryCache
public TeamsHostedService(HttpClient httpClient, ILogger<TeamsHostedService> logger, IMemoryCache cache)
{
    _httpClient = httpClient;
    _logger = logger;
    _cache = cache;
}

public async Task<string> GetImageAsBase64(string url, int retryCount = 3)
{
    var cacheKey = $"TeamsImage_{url}";
    // 优先读取缓存
    if (_cache.TryGetValue(cacheKey, out string cachedBase64))
    {
        return cachedBase64;
    }
    
    // 原有请求逻辑...
    var base64Result = Convert.ToBase64String(imageBytes);
    
    // 缓存结果，设置7天滑动过期
    var cacheOptions = new MemoryCacheEntryOptions()
        .SetSlidingExpiration(TimeSpan.FromDays(7));
    _cache.Set(cacheKey, base64Result, cacheOptions);
    
    return base64Result;
}

4. 控制并发请求数 #

通过SemaphoreSlim限制同时发起的图片请求数量，避免短时间内请求量过载：

private readonly SemaphoreSlim _requestSemaphore = new SemaphoreSlim(5); // 限制同时5个请求

public async Task<string> GetImageAsBase64(string url, int retryCount = 3)
{
    await _requestSemaphore.WaitAsync();
    try
    {
        // 原有请求+缓存逻辑...
    }
    finally
    {
        _requestSemaphore.Release();
    }
}

5. 确认应用权限配置 #

确保你的应用使用应用权限（如ChannelMessage.Read.All）而非委派权限，应用权限的限流阈值更高，能有效降低429触发概率。同时需确认Azure AD中已完成权限的管理员同意配置。

内容的提问来源于stack exchange，提问作者traveling-waffles