配置HttpClient与Polly策略后超时异常捕获但不重试问题
问题原因及解决方案
核心原因
HttpClient超时是全局总超时
你配置的client.Timeout = TimeSpan.FromSeconds(10)是整个HttpClient请求流程的总时间限制,包含Polly所有重试步骤的耗时。当第一次请求耗尽10秒触发超时后,HttpClient会立即触发CancellationToken取消整个操作,此时Polly的重试逻辑即使已经触发OnRetry回调,也会被强制终止,无法执行实际的重试请求。异常匹配的精准度问题
HttpClient超时抛出的是TaskCanceledException(而非你预期的TimeoutException),HandleTransientHttpError()默认不处理这类取消异常。你用OrInner<Exception>虽然能宽泛捕获到异常,但总超时的限制已经导致后续重试操作被直接打断。
解决方案
方案一:用Polly超时策略替代HttpClient全局超时(推荐)
移除HttpClient的Timeout配置,改用Polly的TimeoutPolicy为每个单独的重试请求设置超时,确保重试流程不受总超时限制:
services .AddHttpClient<ISomeHttpService, SomeHttpService>(client => { client.BaseAddress = new Uri(configuration.BaseAddress); // 移除全局Timeout配置 }) .AddPolicyHandler(GetPollyPolicy()) .AddHttpMessageHandler<DistributedCachedHttpClientHandler>(); // ..... private static IAsyncPolicy<HttpResponseMessage> GetPollyPolicy() { // 为每个单独请求设置10秒超时 var perRequestTimeout = Policy.TimeoutAsync<HttpResponseMessage>(TimeSpan.FromSeconds(10)); // 重试策略:捕获瞬时错误+请求取消异常 var retryPolicy = HttpPolicyExtensions .HandleTransientHttpError() .Or<TaskCanceledException>() .WaitAndRetryAsync(2, _ => TimeSpan.FromMilliseconds(100), (exception, timeSpan) => { _ = "breakpoint"; }); // 组合策略:先执行单请求超时,再执行重试 return Policy.WrapAsync(retryPolicy, perRequestTimeout); }
方案二:调整HttpClient全局超时为足够大的值
如果你需要保留HttpClient全局超时,需将其设置为远大于重试总耗时的数值(比如30秒,覆盖3次请求+2次间隔的总时间),同时明确捕获TaskCanceledException:
services .AddHttpClient<ISomeHttpService, SomeHttpService>(client => { client.BaseAddress = new Uri(configuration.BaseAddress); // 设置总超时为30秒,覆盖所有重试步骤 client.Timeout = TimeSpan.FromSeconds(30); }) .AddPolicyHandler(GetPollyPolicy()) .AddHttpMessageHandler<DistributedCachedHttpClientHandler>(); // ..... private static IAsyncPolicy<HttpResponseMessage> GetPollyPolicy() { return HttpPolicyExtensions .HandleTransientHttpError() .Or<TaskCanceledException>() // 明确捕获超时取消异常 .WaitAndRetryAsync(2, _ => TimeSpan.FromMilliseconds(100), (exception, timeSpan) => { _ = "breakpoint"; }); }
内容的提问来源于stack exchange,提问作者mnj
相关产品推荐
相关产品推荐

