The simple reason is that the compiler has to be able to statically verify that all execution flow paths end up with a return statement (or an exception). Let’s look at your code, it contains: Some variables controlling a while loop A while loop, with the return statement embedded No return statement after the loop … Read more
Yes, you need to add a reference to System.Net.Http.Formatting.dll This can be found in the extensions assemblies area. A good way of achieving this is by adding the NuGet package Microsoft.AspNet.WebApi.Client to your project.
Please read the caveats at the end of this answer as to why HTTP GET requests with bodies are, in general, not advised. If you are using .NET Core, the standard HttpClient can do this out-of-the-box. For example, to send a GET request with a JSON body: HttpClient client = … … var request = … Read more
I have found the answer to my question. client.DefaultRequestHeaders.Add(“X-Version”,”1″); That should add a custom header to your request
The reason you are experiencing this behavior is that it is by design. Most HTTP clients (by default) strip out authorization headers when following a redirect. One reason is security. The client could be redirected to an untrusted third party server, one that you would not want to disclose your authorization token to. What you … Read more
You need to use: await client.PostAsync(uri, content); Something like that: var comment = “hello world”; var questionId = 1; var formContent = new FormUrlEncodedContent(new[] { new KeyValuePair<string, string>(“comment”, comment), new KeyValuePair<string, string>(“questionId”, questionId) }); var myHttpClient = new HttpClient(); var response = await myHttpClient.PostAsync(uri.ToString(), formContent); And if you need to get the response after post, … Read more
There’s 2 likely reasons that a TaskCanceledException would be thrown: Something called Cancel() on the CancellationTokenSource associated with the cancellation token before the task completed. The request timed out, i.e. didn’t complete within the timespan you specified on HttpClient.Timeout. My guess is it was a timeout. (If it was an explicit cancellation, you probably would … Read more
Create a HttpRequestMessage, set the Method to GET, set your headers and then use SendAsync instead of GetAsync. var client = new HttpClient(); var request = new HttpRequestMessage() { RequestUri = new Uri(“http://www.someURI.com”), Method = HttpMethod.Get, }; request.Headers.Accept.Add(new MediaTypeWithQualityHeaderValue(“text/plain”)); var task = client.SendAsync(request) .ContinueWith((taskwithmsg) => { var response = taskwithmsg.Result; var jsonTask = response.Content.ReadAsAsync<JsonObject>(); jsonTask.Wait(); … Read more
It turns out that, out of the four possible permutations of including or excluding trailing or leading forward slashes on the BaseAddress and the relative URI passed to the GetAsync method — or whichever other method of HttpClient — only one permutation works. You must place a slash at the end of the BaseAddress, and … Read more
It is matter of ServicePoint. Which provides connection management for HTTP connections. The default maximum number of concurrent connections allowed by a ServicePoint object is 2. So if you need to increase it you can use ServicePointManager.DefaultConnectionLimit property. Just check the link in MSDN there you can see a sample. And set the value you … Read more