dotnet-httpclient

My HttpClient uses digest authentication to connect to the server and expects search queries in response. These search queries can come in any time so the client is expected to leave the connection open at all times. The connection is made using the following code: public static async void ListenForSearchQueries(int resourceId) { var url = $"xxx/yyy/{resourceId}/waitForSearchRequest?token=abc"; var httpHandler = new HttpClientHandler { PreAuthenticate = true }; using (var digestAuthMessageHandler = new DigestAuthMessageHandler(httpHandler, "user", "password")) using (var client = new

Follow-up to this question . I have a library with many async methods that thinly wrap HttpClient . Effectively they just do some setup and directly return the Task returned from the HttpClient call: public Task DoThingAsyc() { // do some setup return httpClient.DoThingAsync(); } I'm pondering whether to add ConfigureAwait(false) to these calls. The prevailing wisdom seems to be "yes, always do that in libraries." But in this case, it would introduce some (perhaps negligible) overhead, because ConfigureAwait returns a ConfiguredTaskAwaitable which would need to be wrapped back into a Task in

I'm using Microsoft HTTP Client Libraries from NuGet and I'm basically trying to allow TLS authentication in HttpClient using X509Certificate2 certificates. I have tried creating the client like this: WebRequestHandler certHandler = new WebRequestHandler () { ClientCertificateOptions = ClientCertificateOption.Manual, UseDefaultCredentials = false }; certHandler.ClientCertificates.Add (this.ClientCertificate); HttpClient client = new HttpClient (certHandler); However certHandler.ClientCertificates is failing because this getter is not implemented in Mono , so I get a NotImplementedException

I would like to create a demo login service in web api and need to set a cookie on the response. How do I do that? Or are there any better way to do authorization? Add a reference to System.Net.Http.Formatting.dll and use the AddCookies extension method defined in the HttpResponseHeadersExtensions class. Here is a blog post describing this approach , and the MSDN topic . If that assembly isn't an option for you, here's my older answer from before this was an option: Older answer follows I prefer an approach that stays within the realm of HttpResponseMessage without bleeding into the

Our MVC application calls a WebAPI action using HttpClient. I decided to inject the HttpClient using StructureMap and override dispose in the controller public HomeController(HttpClient httpClient) { _httpClient = httpClient; } protected override void Dispose(bool disposing) { if (disposing && _httpClient != null) { _httpClient.Dispose(); } base.Dispose(disposing); } The StructureMap ObjectInitialize basically looks like this.. x.For<HttpClient>().Use(() => new HttpClient() { BaseAddress = "my/uri/"}); When I build this, CodeAnalysis complains "Dispose objects before losing scope" and points

I have a ASP.NET Core 2.0 webservice running on IIS. One of controller's methods looks more or less like this: [HttpGet()] public IActionResult Test() { // do some db updates and get data var result = DoSomeStuff(); // serialize data to byte array var output = Serialize(result); return File(output, "application/octet-stream"); } It does some database updates, query records from a table, serialize data and send them as a response. Data are sent in binary format. I'm using MessagePack-CSharp as a serializer. Then I have client application that communicates with this webservice. It's .NET

I am sending request that can be significantly big(~1Mb) and I am seeing a large delay betweeen when I make the request and when asp.net core logs that it is handling the request. I think I can cut down this time by compressing the request to asp using gzip. Below is the fairly straight forward way that I am making requests without compression. What is the proper way to implement Gzip request compression on the client requesting side, and once I implement it on the client, what do I need to do for the server side? using (HttpResponseMessage response = client.PostAsync("Controller/Action",