.NET Core HttpClient DefaultRequestHeaders丢失致API调用异常求助

问题根源 #

你的代码中使用AsParallel().ForAll()并行遍历字典，向HttpClient.DefaultRequestHeaders添加请求头，但**DefaultRequestHeaders的Add方法并非线程安全**。多线程同时修改这个集合时，会出现竞态条件，导致部分请求头的添加操作被覆盖或丢失，这就是为什么到达API的请求头数量不稳定、调用结果时好时坏的原因。

修复方案 #

1. 替换并行遍历为顺序遍历 #

直接使用普通foreach循环逐个添加请求头，避免多线程竞争：

public bool CheckBackEndConnection(Dictionary<string, string> backendConfig, out string errorMessage)
{
    var result = false;
    errorMessage = string.Empty;

    using (var client = new HttpClient())
    {
        // 移除并行操作，改为顺序遍历
        foreach (var record in backendConfig)
        {
            client.DefaultRequestHeaders.Add(record.Key, record.Value);
        }

        var response = client.GetAsync(new Uri(backendConfig[nameof(Dev_BackendConfig.INTEGRATIONURL)] + "ConnectToBackEnd")).Result;
        result = response.IsSuccessStatusCode;

        if (!result)
        {
            errorMessage = "API CheckBackEndConnection " + response.Content.ReadAsStringAsync().Result;
        }
    }

    return result;
}

2. 进阶优化：改用异步模式避免阻塞 #

原代码使用.Result同步阻塞HTTP请求，存在死锁风险，建议改为异步/await模式：

public async Task<bool> CheckBackEndConnectionAsync(Dictionary<string, string> backendConfig, out string errorMessage)
{
    var result = false;
    errorMessage = string.Empty;

    using (var client = new HttpClient())
    {
        foreach (var record in backendConfig)
        {
            client.DefaultRequestHeaders.Add(record.Key, record.Value);
        }

        var requestUrl = backendConfig[nameof(Dev_BackendConfig.INTEGRATIONURL)] + "ConnectToBackEnd";
        var response = await client.GetAsync(new Uri(requestUrl));
        result = response.IsSuccessStatusCode;

        if (!result)
        {
            errorMessage = "API CheckBackEndConnection " + await response.Content.ReadAsStringAsync();
        }
    }

    return result;
}

3. 可选优化：在请求消息上单独设置头（避免污染客户端默认头） #

如果后续需要复用HttpClient，建议直接在HttpRequestMessage上设置请求头，而不是修改客户端的默认头，防止不同请求之间的头互相干扰：

public async Task<bool> CheckBackEndConnectionAsync(Dictionary<string, string> backendConfig, out string errorMessage)
{
    var result = false;
    errorMessage = string.Empty;

    using (var client = new HttpClient())
    {
        var requestUrl = backendConfig[nameof(Dev_BackendConfig.INTEGRATIONURL)] + "ConnectToBackEnd";
        var request = new HttpRequestMessage(HttpMethod.Get, new Uri(requestUrl));

        foreach (var record in backendConfig)
        {
            // 跳过URL对应的配置项，不添加到请求头
            if (record.Key == nameof(Dev_BackendConfig.INTEGRATIONURL))
                continue;
            request.Headers.Add(record.Key, record.Value);
        }

        var response = await client.SendAsync(request);
        result = response.IsSuccessStatusCode;

        if (!result)
        {
            errorMessage = "API CheckBackEndConnection " + await response.Content.ReadAsStringAsync();
        }
    }

    return result;
}

关于首次失败二次成功的说明 #

这是并行执行的随机性导致的偶然现象：有时并行操作的线程竞争程度低，刚好所有请求头都被成功添加；但大多数情况下，多线程修改非线程安全集合会导致部分请求头丢失，触发API的“缺少请求头”错误。

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