Handling network disconnect

Question

I am trying to do "long polling" with an HttpWebRequest object.

In my C# app, I am making an HTTP GET request, using HttpWebRequest. And then afterwards, I wait for the response with beginGetResponse(). I am using ThreadPool.RegisterWaitForSingleObject to wait for the response, or to timeout (after 1 minute).

I have set the target web server to take a long time to respond. So that, I have time to disconnect the network cable.

After sending the request, I pull the network cable.

Is there a way to get an exception when this happens? So I don't have to wait for the timeout?

Instead of an exception, the timeout (from RegisterWaitForSingleObject) happens after the 1 minute timeout has expired.

Is there a way to determine that the network connection went down? Currently, this situation is indistinguishable from the case where the web server takes more than 1 minute to respond.

jm. · Accepted Answer · 2012-02-24T03:44:46.403

I found a solution:

Before calling beginGetResponse, I can call the following on the HttpWebRequest:

req.ServicePoint.SetTcpKeepAlive( true, 10000, 1000)

I think this means that after 10 seconds of inactivity, the client will send a TCP "keep alive" over to the server. That keep alive will fail if the network connection is down because the network cable was pulled.

So, when the cable is pulled, I a keep alive gets sent within 10 seconds (at most), and then the callback for BeginGetResponse happens. In the callback, I get and exception when I call req.EndGetResponse().

I guess this defeats one of the benefits of long polling, though. Since we're still sending packets around.

score 3 · Answer 2 · answered Feb 09 '12 at 20:41

I'll leave it to you to try pulling the plug on this.

ManualResetEvent done = new ManualResetEvent(false);

void Main()
{        
    // set physical address of network adapter to monitor operational status
    string physicalAddress = "00215A6B4D0F";

    // create web request
    var request = (HttpWebRequest)HttpWebRequest.Create(new Uri("http://stackoverflow.com"));

    // create timer to cancel operation on loss of network
    var timer = new System.Threading.Timer((s) => 
    {
        NetworkInterface networkInterface = 
            NetworkInterface.GetAllNetworkInterfaces()
                .FirstOrDefault(nic => nic.GetPhysicalAddress().ToString() == physicalAddress);

        if(networkInterface == null)
        {
            throw new Exception("Could not find network interface with phisical address " + physicalAddress + ".");
        }
        else if(networkInterface.OperationalStatus != OperationalStatus.Up)
        {
            Console.WriteLine ("Network is down, aborting.");
            request.Abort();
            done.Set();
        }
        else
        {
            Console.WriteLine ("Network is still up.");
        }
    }, null, 100, 100);

    // start asynchronous request
    IAsyncResult asynchResult = request.BeginGetResponse(new AsyncCallback((o) =>
    {
        try
        {           
            var response = (HttpWebResponse)request.EndGetResponse((IAsyncResult)o); 
            var reader = new StreamReader(response.GetResponseStream(), System.Text.Encoding.UTF8);
            var writer = new StringWriter();
            writer.Write(reader.ReadToEnd());
            Console.Write(writer.ToString());
        }
        finally
        {
            done.Set();
        }
    }), null);

    // wait for the end
    done.WaitOne();
}

score 2 · Answer 3 · edited May 23 '17 at 12:08

2

I dont think you are gonna like this. You can test for internet connectivity after you create the request to the slow server.

There are many ways to do that - from another request to google.com (or some ip address in your network) to P/Invoke. You can get more info here: Fastest way to test internet connection

After you create the original request you go in a loop that checks for internet connectivity and until either the internet is down or the original request comes back (it can set a variable to stop the loop).

Helps at all?

edited May 23 '17 at 12:08

Community

1
1

answered Feb 09 '12 at 19:01

Yannis

6,047
5
43
62

It helps a little, but it seems like the HttpWebRequest ought to know (sooner or later) if it's TCP connection has gone down. – jm. Feb 09 '12 at 19:27
why dont you extend the HttpWebRequest to add this functionality? but if you are asking about the native .NET framework then no I dont think HttpWebRequest contains such a feature. – Yannis Feb 09 '12 at 19:37

Handling network disconnect

3 Answers3

Linked