I had the same issue (Windows 10 and SSL3 / TLS only… not System Default) with a legacy app targeting 4.7.2. My issue was that during the upgrade process over the years we never added in the targetFramework to the system.web > httpRuntime element (Note: it did exist on system.web > compilation element). Before taking … Read more
CookieContainers can hold multiple cookies for different websites, therefor a label (the Domain) has to be provided to bind each cookie to each website. The Domain can be set when instantiating the individual cookies like so: Cookie chocolateChip = new Cookie(“CookieName”, “CookieValue”) { Domain = “DomainName” }; An easy way to grab the domain to … Read more
if (Request.Headers[“XYZComponent”].Count() > 0) … will attempted to count the number of characters in the returned string, but if the header doesn’t exist it will return NULL, hence why it’s throwing an exception. Your second example effectively does the same thing, it will search through the collection of Headers and return NULL if it doesn’t … Read more
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 … Read more
Yes, it supports it but you must explicitly set the TLS version on the ServicePointManager. Just have this code run anytime (in same app domain) before you make the call to Experian: System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12 Update see @iignatov ‘s answer for what you must do for framework v4.0. My code works with 4.5+
Are all (or most) of your requests going to the same host by any chance? There’s a built-in limit on a per-host basis. You can change this in app.config in the system.Net connectionManagement element. The other thing is that the thread pool only ramps up its number of threads gradually – it starts a new … Read more
My preferred way is this. It handles the escaping and parsing for you. WebClient webClient = new WebClient(); webClient.QueryString.Add(“param1”, “value1”); webClient.QueryString.Add(“param2”, “value2”); string result = webClient.DownloadString(“http://theurl.com”);
What I have found to be the main culprit with slow web requests is the proxy property. If you set this property to null before you call the GetResponse method the query will skip the proxy autodetect step: request.Proxy = null; using (var response = (HttpWebResponse)request.GetResponse()) { } The proxy autodetect was taking up to … Read more
You must subclass and override one or more functions. class MyWebClient : WebClient { protected override WebRequest GetWebRequest(Uri address) { HttpWebRequest request = (HttpWebRequest)base.GetWebRequest(address); request.ClientCertificates.Add(new X509Certificate()); return request; } }
SSL is a must. POST method is not more secure than GET as it also gets sent unencrypted over network. SSL will cover the whole HTTP communication and encrypt the HTTP data being transmitted between the client and the server.