From 3bcc95cc2648722dc7aaedaf151ef69fd78076b8 Mon Sep 17 00:00:00 2001 From: mahpate <93220967+mahpate@users.noreply.github.com> Date: Wed, 17 Aug 2022 13:32:00 -0700 Subject: [PATCH] Bug fix for connection leak in SocketsHttpHandler See https://github.com/dotnet/runtime/issues/66673#issuecomment-1073811798 --- src/ReverseProxy/Forwarder/ForwarderHttpClientFactory.cs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/ReverseProxy/Forwarder/ForwarderHttpClientFactory.cs b/src/ReverseProxy/Forwarder/ForwarderHttpClientFactory.cs index 5c322a346..2f4178088 100644 --- a/src/ReverseProxy/Forwarder/ForwarderHttpClientFactory.cs +++ b/src/ReverseProxy/Forwarder/ForwarderHttpClientFactory.cs @@ -48,7 +48,7 @@ public HttpMessageInvoker CreateClient(ForwarderHttpClientContext context) AutomaticDecompression = DecompressionMethods.None, UseCookies = false, ActivityHeadersPropagator = new ReverseProxyPropagator(DistributedContextPropagator.Current), - + ConnectTimeout = TimeSpan.FromSeconds(15), // See: https://github.com/dotnet/runtime/issues/66673#issuecomment-1073811798 // NOTE: MaxResponseHeadersLength = 64, which means up to 64 KB of headers are allowed by default as of .NET Core 3.1. };