Httpclient在.net core3.1上成功运行，但更新到.net 5中连接超时(System.Net.Sockets.SocketException (10060)) C#

Posted 2021-06-24 不会敲代码的蒋大帅哥

tags:

篇首语：本文由小常识网(cha138.com)小编为大家整理，主要介绍了Httpclient在.net core3.1上成功运行，但更新到.net 5中连接超时(System.Net.Sockets.SocketException (10060)) C#相关的知识，希望对你有一定的参考价值。

前言：

项目本来是在.net core 3.0 版本上跑然后看了看现在都到5.0马上6.0了想着升级一下体验一下新版本的高性能（狗头）然后在测试的时候发现项目里一些请求外部API出现大批请求超时错误如下。没想到刚升级就出岔子了，使用同样的代码在本地运行，环境一致的情况下，将SDK换成.net core 3.0 请求正常，切换到5.0时就开始请求连接超时，没办法先百度看看有没有病友，结果发现就我一个病友，哎，本来有的话就不想发了，但是看到没有有用的结果，我还是把我搜索到的一些结果分享给广大病友，希望能有一点帮助把！

Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1]
      An unhandled exception has occurred while executing the request.
      System.Net.Http.HttpRequestException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (api.map.baidu.com:80)
       ---> System.Net.Sockets.SocketException (10060): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
         at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|283_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.DefaultConnectAsync(SocketsHttpConnectionContext context, CancellationToken cancellationToken)
         at System.Net.Http.ConnectHelper.ConnectAsync(Func`3 callback, DnsEndPoint endPoint, HttpRequestMessage requestMessage, CancellationToken cancellationToken)
         --- End of inner exception stack trace ---
         at System.Net.Http.ConnectHelper.ConnectAsync(Func`3 callback, DnsEndPoint endPoint, HttpRequestMessage requestMessage, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
         at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
         at Microsoft.Extensions.Http.Logging.LoggingScopeHttpMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
         at System.Net.Http.HttpClient.SendAsyncCore(HttpRequestMessage request, HttpCompletionOption completionOption, Boolean async, Boolean emitTelemetryStartStop, CancellationToken cancellationToken)
         at MarineSH.Utils.HttpClientHelper.GetAsync(String url, Dictionary`2 headers) in D:\\wwwroot\\2021\\MarineSH\\MarineSH.Utils\\HttpClientHelper.cs:line 37
         at MarineSH.Core.Service.BaiduApiService.Iidentifyaddress(String txtAddress) in D:\\wwwroot\\2021\\MarineSH\\MarineSH.Core\\Service\\BaiduApiService.cs:line 26
         at MarineSH.Controllers.GraphApiController.getADD(String add) in D:\\wwwroot\\2021\\MarineSH\\MarineSH\\Controllers\\GraphApiController.cs:line 23
         at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.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|19_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.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
         at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
         at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
         at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

回归正言，通过错误我们可以发现是在连接上出现了问题，那么最有可能就是tcp握手期间没有得到任何响应，然后我又对我本地端口进行查看，发现都是正常的没有问题，然后在github的.net rutime 项目的Issues中发现这个问题还是有很多人出现的。在查看了一些回复后可以确定问题是由于.net 5中切换到了双协议栈,TcpClient将默认为IPV6，这意味这IPV6将用于IPV4和IPV6的请求，这个时候如果你的客户端或者网络不支持IPV6或双协议栈，连接将会出现超时。 ==>Httpclient perfectly work on 3.1 but timeout in .net 5

IPv6 测试 (test-ipv6.com) 这个网址可以测试你当前网络是否支持IPV6连接，这个测试结果似乎没什么用，后来我回家测试也发现显示的也是同样的报告，但是在家使用同样的代码连接都没问题，那么最有可能是公司vpn网络的原因。

解决方案和后续

（下方截图原地址 https://github.com/dotnet/runtime/issues/44686 ）

这个问题的解决方案,net runtime团队给出了原因和建议，大概的意思根本原因是由于3.0升级到5.0之后，HttpClient使用双栈套接字所造成的

Httpclient在.net core3.1上成功运行，但更新到.net 5中连接超时(System.Net.Sockets.SocketException (10060)) C#

前言：

解决方案和后续

（下方截图原地址 https://github.com/dotnet/runtime/issues/44686 ）

相关代码