Private const string ClientUserAgent = 'my-api-client-v1' Private HttpClientHandler _httpClientHandler You need to install package Newtonsoft.Json > using Newtonsoft.Json Reuse Httpclient as much as possible using System Do NOT recreate HTTPClient for each request. It's safe to reuse because it's stateless. Register this object as singleton to your dependency injection library. This is my ApiClient which creates the HttpClient for only once.

See following thread for more informationĭo HttpClient and HttpClientHandler have to be disposed? HttpClient is preferred over HttpWebRequest due to async methods available out of the box and you would not have to worry about writing begin/end methods.īasically when you use async call (using either of the class), it will not block the resources waiting for the response and any other request would utilise the resources to make further calls.Īnother thing to keep in mind that you should not be using HttpClient in the 'using' block to allow reuse of same resources again and again for other web requests.

If you use either of them with async it should be good for the performance point of view as it will not block the resources waiting for the response and you will get good throughput. Tags : c#,asp.net-web-api,httpwebrequest,httpclient I would appreciate any help in making me understand which approach I should take so as to achieve max performance, minimizing connections and making sure security is not impacted. Using (HttpClient client = new HttpClient(GetWebRequestHandler(), false))ī) using (HttpClient client = new HttpClient)Ĭ) HttpWebRequest req = (HttpWebRequest)WebRequest.Create( 'some uri string') WebRequestHandler handler = new WebRequestHandler Possible implementations that I tried out are shown belowĪ) private WebRequestHandler GetWebRequestHandler()ĬredentialCache credentialCache = new CredentialCache() ĬredentialCache.Add(ResourceUriCanBeAnyUri, 'NTLM', CredentialCache.DefaultNetworkCredentials)

The following article summarizes the high-speed NTLM-authenticated connection sharing: HttpWebRequest.UnsafeAuthenticatedConnectionSharing I also looked up some documentation on other ways to use HttpClient in examples. WebRequest needs to recreate the connection for each request. If shared, and the requests are to the same destination, multiple requests could reuse the connections. I discovered that a single HttpClient could be shared by multiple requests.

Webrequest vs httpclient