I noticed that an HttpWebRequest hangs on the first request. I did some research and what seems to be happening is that the request is configuring or auto-detecting proxies. If you set request.Proxy = null; on the web request object, you might be able to avoid an initial delay. With proxy auto-detect: using (var response … Read more
HttpWebRequest may be taking a while to detect your proxy settings. Try adding this to your application config: <system.net> <defaultProxy enabled=”false”> <proxy/> <bypasslist/> <module/> </defaultProxy> </system.net> You might also see a slight performance gain from buffering your reads to reduce the number of calls made to the underlying operating system socket: using (BufferedStream buffer = … Read more
Assuming the problem is that you’re having a hard time getting to the returned content, the easiest path would likely be using async/await if you can use it. Even better would be to switch to HttpClient if you’re using .NET 4.5 since it’s ‘natively’ async. Using .NET 4 and C# 4, you can still use … Read more
Something like this should work (untested): public static class Extensions { public static async Task<HttpWebResponse> GetResponseAsync(this HttpWebRequest request, CancellationToken ct) { using (ct.Register(() => request.Abort(), useSynchronizationContext: false)) { var response = await request.GetResponseAsync(); ct.ThrowIfCancellationRequested(); return (HttpWebResponse)response; } } } In theory, if cancellation is requested on ct and request.Abort is invoked, await request.GetResponseAsync() should throw … Read more
Is this possible using HttpWebRequest and HttpWebResponse? You could have your web server simply catch and write the exception text into the body of the response, then set status code to 500. Now the client would throw an exception when it encounters a 500 error but you could read the response stream and fetch the … Read more
Using HttpWebRequest gives you more control on the request. You can set cookies, headers, protocol, etc… In the response, you can also retrieve the cookies and headers
The Fiddler FAQ gives the answer to this. You essentially route your HTTP traffic through Fiddler (i.e. Use Fiddler as a proxy). Here’s some links that will help: Fiddler Web Debugging – Configuring Clients Which in turn links to here: Take the Burden Off Users with Automatic Configuration in .NET You can achieve this via … Read more
Note that RFC 6266 supersedes the RFCs referenced below. Section 7 outlines some of the related security concerns. The authority on the content-disposition header is RFC 1806 and RFC 2183. People have also devised content-disposition hacking. It is important to note that the content-disposition header is not part of the HTTP 1.1 standard. The HTTP … Read more
It is easy using Json.Net. Just declare your concrete classes and then deserialize. var root = JsonConvert.DeserializeObject<RootObject>(yourJsonString); foreach (var item in root.TotalUsersCount) { Console.WriteLine(item.AccountStatus); } var allusers = root.TotalUsersCount.Sum(u => u.TotalUsers); public class TotalUsersCount { public int AccountStatus { get; set; } public int TotalUsers { get; set; } public int MemberUsers { get; set; … Read more