CODEWITHSUNDEEP
c#.nethttphttps
Mike Moore
Mike Moore

Reputation: 1340

HTTPS web request failing

When I run the program contained below the first HTTPS request succeeds, but the second request fails. Both url's are valid and both can be accessed successfully in a browser. Any suggestions as to what needs to be done to access the second url successfully?

using System;
using System.IO;
using System.Net;

public class Program
{
    private static void Main(string[] args)
    {
        var content = "";
        bool status;
        var url1 = "https://mail.google.com";
        var url2 = "https://my.ooma.com";
        status = DoHttpRequest(url1, out content);
        OutputStatus(url1, status, content);
        status = DoHttpRequest(url2, out content);
        OutputStatus(url2, status, content);
        Console.ReadLine();
    }

    private static void OutputStatus(string url, bool status, string content)
    {
        if (status) Console.WriteLine("Url={0}, Status=Success, content length = {1}", url, content.Length);
        else Console.WriteLine("Url={0}, Status=Fail, ErrorMessage={1}", url, content);
    }

    private static bool DoHttpRequest(string url, out string content)
    {
        content = "";
        var request = (HttpWebRequest) WebRequest.Create(url);
        try
        {
            request.Method = "GET";
            request.CookieContainer = null;
            request.Timeout = 25000; // 25 seconds
            var response = (HttpWebResponse) request.GetResponse();
            var streamReader = new StreamReader(response.GetResponseStream());
            content = streamReader.ReadToEnd();
            return true;
        }
        catch (WebException ex)
        {
            content = ex.Message;
            return false;
        }
    }
}

Upvotes: 2

Views: 4731

Answers (2)

EricLaw
EricLaw

Reputation: 57075

Historically, most problems of this description that I've seen occur when you forget to call .Close() on the object returned from GetResponseStream(). The problem exists because when you forget to close the first request, the second request deadlocks waiting for a free connection.

Typically this hang happens on the 3rd request, not the second.

Update: Looking at your repro, this has nothing to do with the order of the requests. You're hitting a problem because this site is sending a TLS Warning at the beginning of the HTTPS handshake, and .NET will timeout when that occurs. See http://blogs.msdn.com/b/fiddler/archive/2012/03/29/https-request-hangs-.net-application-connection-on-tls-server-name-indicator-warning.aspx. The problem only repros on Windows Vista and later, because the warning is related to a TLS extension that doesn't exist in the HTTPS stack on WinXP.

Upvotes: 3

Min Min
Min Min

Reputation: 6218

Increse your request TimeOut.

request.Timeout = 60000; //60 second.

May be your network connection is a bit slow. I run with 25 seconds, okay. (Yeah, the second url is a bit longer to get response, than the first one.)

Upvotes: 1

Related Questions