调用GRPC API遇RpcException：预期HTTP 200却返回400错误

问题场景 #

通过Basket API调用gRPC服务时，已确认客户端与服务端的服务注册、功能逻辑、连接配置均无问题，但触发调用后抛出如下错误：

Grpc.Core.RpcException: Status(StatusCode=Cancelled, Detail="Bad gRPC response. 
Expected HTTP status code 200. Got status code: 400")
at Grpc.Net.Client.Internal.GrpcCall`2.GetResponseAsync()
at Basket.API.GrpcServices.DiscountGrpcService.GetDiscount(String productName) in 
/xxxx/Basket.API/GrpcServices/DiscountGrpcService.cs:line 18
at Basket.API.Controllers.BasketController.UpdateBasket(ShoppingCart basket) in 
/xxxx/Basket.API/Controllers/BasketController.cs:line 44
at lambda_method5(Closure , Object )
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor
.AwaitableObjectResultExecutor.Execute(IActionResultTypeMapper mapper,  
ObjectMethodExecutor executor, Object controller, Object[] arguments)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker. 
<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, 
ValueTask`1 actionResultValueTask)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker. 
<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task 
lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure
.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& 
next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker. 
<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker, Task 
lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker. 
<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker, Task lastTask, 
State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker. 
<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable 
scope)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker. 
<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable 
scope)
at Microsoft.AspNetCore.Routing.EndpointMiddleware. 
<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger 
logger)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext 
context)
at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext 
httpContext)
at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext 
httpContext, ISwaggerProvider swaggerProvider)
at Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware. 
<Invoke>g__AwaitMatcher|8_0(EndpointRoutingMiddleware middleware, HttpContext 
httpContext, Task`1 matcherTask)
at 
Microsoft.AspNetCore.Diagnostics
.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

排查与解决步骤 #

• 校验请求参数合法性：400错误核心是请求不符合服务端规则，重点检查GetDiscount方法传入的productName参数是否符合proto定义的约束（如是否为空、长度是否超限、是否含非法字符）。
• 启用服务端gRPC日志：在服务端配置Debug级别的gRPC日志，查看完整请求细节，定位参数或格式问题。ASP.NET Core配置示例：

  {
    "Logging": {
      "LogLevel": {
        "Grpc.AspNetCore.Server": "Debug"
      }
    }
  }
  

• 同步客户端与服务端proto文件：确保两端使用的proto文件完全一致，包括服务方法、字段类型及约束，若proto有更新需重新生成代码。
• 排查服务端拦截器/中间件：检查服务端是否存在自定义拦截器或中间件对gRPC请求做额外校验（如权限、参数校验），导致返回400错误。
• 直接测试服务端接口：使用gRPCurl或Postman直接调用服务端的GetDiscount方法，传入相同参数，验证是否能正常响应，排除客户端代码封装问题。
• 确认HTTP/2配置有效性：gRPC依赖HTTP/2，检查服务端是否启用HTTP/2，客户端通道是否配置支持HTTP/2（如使用GrpcChannel.ForAddress创建通道）。

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