.NET Core微服务间调用Web API时用户上下文为空问题

微服务间通过HttpClient调用时，目标服务拿不到用户上下文的核心原因是：HttpClient默认不会自动携带当前请求中的用户上下文相关HTTP头（比如Authorization令牌、自定义用户标识头这类），而Postman/UI调用时是手动或前端自动带上了这些头，所以目标服务能正常获取。

下面是具体的解决办法：

1. 手动传递用户上下文头信息 #

在发起HttpClient请求前，从当前请求的HttpContext中提取关键头信息，手动添加到请求消息里：

// 需先注入IHttpContextAccessor来获取当前请求上下文
var currentHeaders = _httpContextAccessor.HttpContext.Request.Headers;

// 改用HttpRequestMessage构建请求，而非直接调用PostAsync
var request = new HttpRequestMessage(HttpMethod.Post, url);
request.Content = new StringContent(requestParams, Encoding.UTF8, "application/json");

// 复制用户上下文相关的头，比如Authorization、自定义的X-User-Id等
if (currentHeaders.ContainsKey("Authorization"))
{
    request.Headers.Add("Authorization", currentHeaders["Authorization"].ToArray());
}
if (currentHeaders.ContainsKey("X-User-Id"))
{
    request.Headers.Add("X-User-Id", currentHeaders["X-User-Id"].ToArray());
}

var response = await _httpClient.SendAsync(request);

注意：要先在Program.cs/Startup.cs中注册IHttpContextAccessor：

builder.Services.AddHttpContextAccessor();

2. 用自定义Handler自动传递头（批量场景推荐） #

如果多个接口都需要传递用户上下文，写一个自定义的DelegatingHandler自动复制头，避免重复代码：

public class UserContextHandler : DelegatingHandler
{
    private readonly IHttpContextAccessor _httpContextAccessor;

    public UserContextHandler(IHttpContextAccessor httpContextAccessor)
    {
        _httpContextAccessor = httpContextAccessor;
    }

    protected override async Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
    {
        var currentContext = _httpContextAccessor.HttpContext;
        if (currentContext != null)
        {
            // 自动复制Authorization头
            if (currentContext.Request.Headers.TryGetValue("Authorization", out var authHeader))
            {
                request.Headers.TryAddWithoutValidation("Authorization", authHeader.ToString());
            }
            // 可添加其他需要传递的自定义头
            if (currentContext.Request.Headers.TryGetValue("X-User-Context", out var userContextHeader))
            {
                request.Headers.TryAddWithoutValidation("X-User-Context", userContextHeader.ToString());
            }
        }

        return await base.SendAsync(request, cancellationToken);
    }
}

然后将这个Handler注册到HttpClient：

builder.Services.AddHttpClient("UserContextClient")
    .AddHttpMessageHandler<UserContextHandler>();

使用时通过IHttpClientFactory获取命名HttpClient：

private readonly IHttpClientFactory _httpClientFactory;

public YourService(IHttpClientFactory httpClientFactory)
{
    _httpClientFactory = httpClientFactory;
}

// 调用逻辑
var client = _httpClientFactory.CreateClient("UserContextClient");
var request = new HttpRequestMessage(HttpMethod.Post, url);
request.Content = new StringContent(requestParams, Encoding.UTF8, "application/json");
var response = await client.SendAsync(request);

3. 校验目标服务的上下文读取逻辑 #

确认目标服务的contextBuilder.Build方法是从请求头中读取用户上下文，而非依赖Session这类微服务间不适用的机制。如果是读取Cookie，需要给HttpClient配置CookieContainer来传递，但微服务间更推荐用令牌（JWT）作为上下文载体。

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