Adjusting HttpWebRequest Connection Timeout in C#

by

I believe that the problem is that the WebRequest measures the time only after the request is actually made. If you submit multiple requests to the same address then the ServicePointManager will throttle your requests and only actually submit as many concurrent connections as the value of the corresponding ServicePoint.ConnectionLimit which by default gets the value from ServicePointManager.DefaultConnectionLimit. Application CLR host sets this to 2, ASP host to 10. So if you have a multithreaded application that submits multiple requests to the same host only two are actually placed on the wire, the rest are queued up.

I have not researched this to a conclusive evidence whether this is what really happens, but on a similar project I had things were horrible until I removed the ServicePoint limitation.

Another factor to consider is the DNS lookup time. Again, is my belief not backed by hard evidence, but I think the WebRequest does not count the DNS lookup time against the request timeout. DNS lookup time can show up as very big time factor on some deployments.

And yes, you must code your app around the WebRequest.BeginGetRequestStream (for POSTs with content) and WebRequest.BeginGetResponse (for GETs and POSTSs). Synchronous calls will not scale (I won’t enter into details why, but that I do have hard evidence for). Anyway, the ServicePoint issue is orthogonal to this: the queueing behavior happens with async calls too.

More Related Contents:

  1. How to post JSON to a server using C#?
  2. How to add a Timeout to Console.ReadLine()?
  3. How to configure socket connect timeout
  4. Implement C# Generic Timeout
  5. Timeouts with long running ASP.NET MVC Core Controller HTTPPost Method
  6. Post form data using HttpWebRequest
  7. Get host domain from URL?
  8. The operation has timed out at System.Net.HttpWebRequest.GetResponse() while sending large number of requests to a host
  9. How to use httpwebrequest to pull image from website to local file
  10. The request was aborted: Could not create SSL/TLS secure channel
  11. Proxy Basic Authentication in C#: HTTP 407 error
  12. How to add parameters into a WebRequest?
  13. How can you add a Certificate to WebClient (C#)?
  14. how to change originating IP in HttpWebRequest
  15. Is that possible to send HttpWebRequest using TLS1.2 on .NET 4.0 framework
  16. Force HttpWebRequest to send client certificate
  17. HttpWebRequest and forms authentication in C#
  18. GetResponseAsync does not accept cancellationToken
  19. Getting Http Status code number (200, 301, 404, etc.) from HttpWebRequest and HttpWebResponse
  20. Is there a Task based replacement for System.Threading.Timer?
  21. C# HttpWebRequest of type “application/x-www-form-urlencoded” – how to send ‘&’ character in content body?
  22. Receiving JSON data back from HTTP request
  23. How to make an HTTP get request with parameters
  24. TLS 1.2 not negotiated in .NET 4.7 without explicit ServicePointManager.SecurityProtocol call
  25. Getting the Response of a Asynchronous HttpWebRequest
  26. Using HttpWebRequest to POST data/upload image using multipart/form-data
  27. HttpWebRequests sends parameterless URI in Authorization header
  28. Debugging failing HTTPS WebRequest
  29. Why is this WebRequest code slow?
  30. How to know if an HTTP request header value exists

Leave a Comment