httpclientfactory

I am trying to attach an handler to httpclientfactory using "ConfigurePrimaryHttpMessageHandler" but when I look inside the HttpClient to see if the handler is there i cannot find it Am I attaching the handler correctly? Any Suggesions services.AddHttpClient<IGitHubClient,GitHubClient>(client => { client.BaseAddress = new Uri(myUri); client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json")); }) .ConfigurePrimaryHttpMessageHandler(() => new HttpClientHandler { AllowAutoRedirect = false, AutomaticDecompression = DecompressionMethods.Deflate |

I need to add certificate in HttpClientFactory . Old implementation with HttpClient look this: var cookieContainer = new CookieContainer(); var handler = new HttpClientHandler { CookieContainer = cookieContainer }; var basePath = Directory.GetCurrentDirectory(); var certificatePath = Path.Combine(basePath, certPath); var fileExists = File.Exists(certificatePath); if (!fileExists) throw new ArgumentException(certificatePath); var certificate = new X509Certificate2(certificatePath, certPwd); handler.ClientCertificates.Add(certificate); using (var client = new HttpClient(handler)) { client

I want to use the HttpClientFactory that is available in .NET Core 2.1 but I also want to use the HttpClientHandler to utilize the AutomaticDecompression property when creating HttpClients . I am struggling because the .AddHttpMessageHandler<> takes a DelegatingHandler not a HttpClientHandler . Does anyone know how to get this to work? Thanks, Jim Actually I'm not using automatic decompression but the way to achieve this is to properly register http client services.AddHttpClient<MyCustomHttpClient>() .ConfigureHttpMessageHandlerBuilder((c) => new HttpClientHandler() { AutomaticDecompression =

In my asp.net core MVC application, I'm using HttpClientFactory to create HttpClient object for requests to API server. Follows Microsoft document, HttpClient object is created new for each time I call HttpClientFactory.CreateClient() , so it will be safe for setting values to HttpClient.DefaultRequestHeaders . About HttpMessageHandler objects, because they are pooled and can be re-used later. So, if they hold cookies information (For example: setting cookies to HttpClientHandler object), we will violate thread-safe. Is my assumption is correct? How could we deal with this problem? Is it OK if

So, I've registered a named client with the services collection in my Startup.cs: services.AddHttpClient(someServiceName, client => client.BaseAddress = baseAddress); and now can inject an IHttpClientFactory from my service provider. Using this IHttpClientFactory , I conjure up a client instance: var client = httpClientFactory.CreateClient(someServiceName) Once upon a time, it was necessary to be very careful about the disposing of HttpClient instances, as it was rarely the right thing to do . However, now we have HttpClientFactory , does this matter any more? Should/Can this client be

.NET Core 2.1 comes with this new factory called HTTPClientFactory , but I can't figure out how to mock it to unit test some methods that include REST service calls. The factory is being injected using .NET Core IoC container, and what the method does is create a new client from the factory: var client = _httpClientFactory.CreateClient(); And then using the client to get data from a REST service: var result = await client.GetStringAsync(url); The HttpClientFactory is derived from IHttpClientFactory Interface So it is just a matter of creating a mock of the interface var mockFactory = new Mock