All of the Microsoft.Extensions.* packages target .NET Standard 2.0. That means that you can use Dependency Injection, Configuration, Logging and HttpClientFactory if you add the appropriate package to your application. You need to add Microsoft.Extensions.Http to use HttpClientFactory and Microsoft.Extensions.Http.Polly if you want to use it with Polly To configure HttpClientFactory you’ll have to add … Read more
this.startRequest is a delegate that points to StartRequest which in turn uses HttpWebRequest.BeginGetResponse to start async IO. HttpClient is using async IO under the covers, just wrapped in a thread-pool Task. That said, note the following comment in SendAsync // BeginGetResponse/BeginGetRequestStream have a lot of setup work to do before becoming async // (proxy, dns, … Read more
I had the exact same problem myself. It seems the HttpClient just disregards the credentials set in the HttpClientHandler. The following shall work however: using System.Net.Http.Headers; // For AuthenticationHeaderValue const string uri = “https://example.com/path?params=1”; using (var client = new HttpClient()) { var byteArray = Encoding.ASCII.GetBytes(“MyUSER:MyPASS”); var header = new AuthenticationHeaderValue( “Basic”, Convert.ToBase64String(byteArray)); client.DefaultRequestHeaders.Authorization = header; … Read more
Well, HttpResponseMessage.Headers returns an HttpResponseHeaders reference, so you should be able to use GetValues() string error = response.Headers.GetValues(“X-Error”).FirstOrDefault(); string errorCode = response.Headers.GetValues(“X-Error-Code”).FirstOrDefault();
Calling the Dispose method is not required but you can still call it if you need for some reasons. Proof: HttpClient and lifetime management Disposal of the client isn’t required. Disposal cancels outgoing requests and guarantees the given HttpClient instance can’t be used after calling Dispose. IHttpClientFactory tracks and disposes resources used by HttpClient instances. … Read more
Instead of handcranking your models try using something like the Json2csharp.com website. Paste In an example JSON response, the fuller the better and then pull in the resultant generated classes. This, at least, takes away some moving parts, will get you the shape of the JSON in csharp giving the serialiser an easier time and … Read more
The way you are using await/async is poor at best, and it makes it hard to follow. You are mixing await with Task’1.Result, which is just confusing. However, it looks like you are looking at a final task result, rather than the contents. I’ve rewritten your function and function call, which should fix your issue: … Read more
HttpClient is more like a head-less browser. It a powerfull and ideal tool if you are going to be creating many http request. For example you can set default headers and stuff. Here are the top 5 ways it differs from an HttpWebRequest which is taken from here An HttpClient instance is the place to … Read more
So it seems like the calling code needs to know about and take ownership of the response message as well as the stream, or I leave the response message undisposed and let the finalizer deal with it. Neither option feels right. In this specific case, there are no finalizers. Neither HttpResponseMessage or HttpRequestMessage implement a … Read more