Blazor WASM中PostAsJsonAsync返回Bad Request问题求助

此前项目出现AccessTokenNotAvailableException，为未授权用户创建新的HttpClient后，调用PostAsJsonAsync发起请求时，变量result始终返回Bad Request状态码，请求排查解决。

相关代码 #

PublicClient类 #

public class PublicClient
{
    public HttpClient Client { get; }

    public PublicClient(HttpClient httpClient)
    {
        Client = httpClient;
    }

    public async Task<TEntity> Insert<TEntity>(TEntity entity, string controllerName) where TEntity : class
    {
        try
        {
            var result = await Client.PostAsJsonAsync(controllerName, entity);
            result.EnsureSuccessStatusCode();
            string responseBody = await result.Content.ReadAsStringAsync();
            var response = JsonConvert.DeserializeObject<APIEntityResponse<TEntity>>
                (responseBody);
            return response.Data;
            if (response.Success)
                return response.Data;
            else
                return null;
        }
        catch (Exception ex)
        {
            return null;
        }
    }
}

Program.cs中的客户端配置 #

builder.Services.AddHttpClient("BlazorApp.PublicServerAPI", client => client.BaseAddress = new Uri(builder.HostEnvironment.BaseAddress));

builder.Services.AddHttpClient<PublicClient>(client => client.BaseAddress = new Uri(builder.HostEnvironment.BaseAddress));

builder.Services.AddScoped(sp => sp.GetRequiredService<IHttpClientFactory>().CreateClient("BlazorApp.PublicServerAPI"));

排查与解决建议 #

• 清理重复的HttpClient注册
  当前Program.cs同时注册了命名客户端、类型化客户端，还额外创建了一个Scoped的HttpClient实例，这会导致配置冲突。建议简化注册逻辑：

  • 方案一：仅保留类型化客户端注册

    builder.Services.AddHttpClient<PublicClient>(client => 
        client.BaseAddress = new Uri(builder.HostEnvironment.BaseAddress));
    

    后续直接通过构造函数注入PublicClient即可，无需额外注册HttpClient。
  • 方案二：使用命名客户端+IHttpClientFactory
    修改PublicClient依赖IHttpClientFactory：

    public class PublicClient
    {
        private readonly IHttpClientFactory _httpClientFactory;
    
        public PublicClient(IHttpClientFactory httpClientFactory)
        {
            _httpClientFactory = httpClientFactory;
        }
    
        public async Task<TEntity> Insert<TEntity>(TEntity entity, string controllerName) where TEntity : class
        {
            var client = _httpClientFactory.CreateClient("BlazorApp.PublicServerAPI");
            // 原有请求逻辑不变
        }
    }
    

    然后仅注册命名客户端和PublicClient：

    builder.Services.AddHttpClient("BlazorApp.PublicServerAPI", client => 
        client.BaseAddress = new Uri(builder.HostEnvironment.BaseAddress));
    builder.Services.AddScoped<PublicClient>();
    

• 检查请求路径与BaseAddress的拼接
  确认controllerName的格式是否正确：如果BaseAddress已经包含了域名（如https://example.com/），controllerName应以/api/xxx开头，避免出现重复路径（如https://example.comapi/xxx）。可以通过抓包工具查看实际请求URL是否符合后端接口地址。

• 获取Bad Request的具体错误信息
  修改代码捕获错误响应内容，明确后端返回的错误原因：

  try
  {
      var result = await Client.PostAsJsonAsync(controllerName, entity);
      if (!result.IsSuccessStatusCode)
      {
          var errorDetails = await result.Content.ReadAsStringAsync();
          // 输出errorDetails到日志或调试窗口，查看具体错误
      }
      result.EnsureSuccessStatusCode();
      // 原有响应处理逻辑
  }
  catch (Exception ex)
  {
      // 记录异常信息
      return null;
  }
  

  Bad Request通常是请求体格式错误、缺少必填字段或参数类型不匹配，通过错误信息可以快速定位问题。

• 验证请求体与后端DTO的匹配性
  检查TEntity的属性名称、数据类型是否与后端接口接收的DTO完全一致（包括大小写、是否有必填标记）。可以在请求前将entity序列化为JSON字符串，对比后端接口的参数要求。

• 确认请求头配置
  确保HttpClient的请求头符合后端要求，比如添加Accept: application/json：

  builder.Services.AddHttpClient<PublicClient>(client => 
  {
      client.BaseAddress = new Uri(builder.HostEnvironment.BaseAddress);
      client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));
  });
  

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