HttpListener problems: Each HTTP request results in two contexts returned by HttpListener

Question

I have been putting together a little embedded HTTP server in a windows service app that listens for updates coming from other devices on the network that speak HTTP.

For each HTTP request, the code that processes the request/response is executed twice, I expect it to run only once. I tried the code using the AsyncGetContext method and using the synchronous version GetContext - the end result is the same.

Code

public void RunService()
{
    var prefix = "http://*:4333/";
    HttpListener listener = new HttpListener();
    listener.Prefixes.Add(prefix);
    try
    {
        listener.Start();
        _logger.Debug(String.Format("Listening on http.sys prefix: {0}", prefix));
    }
    catch (HttpListenerException hlex)
    {
        _logger.Error(String.Format("HttpListener failed to start listening. Error Code: {0}", hlex.ErrorCode));
        return;
    }
    while (listener.IsListening)
    {
        var context = listener.GetContext(); // This line returns a second time through the while loop for each request
        ProcessRequest(context);
    }
    listener.Close();
}

private void ProcessRequest(HttpListenerContext context) 
{
    // Get the data from the HTTP stream
    var body = new StreamReader(context.Request.InputStream).ReadToEnd();
    _logger.Debug(body);

    byte[] b = Encoding.UTF8.GetBytes("OK");
    context.Response.StatusCode = 200;
    context.Response.KeepAlive = false;
    context.Response.ContentLength64 = b.Length;

    var output = context.Response.OutputStream;
    output.Write(b, 0, b.Length);
    output.Close();
    context.Response.Close();
}

Is there anything obvious that I am missing, I have run out of ideas to track down the issue.

Answer 1

Ok, the issue was I was using a web browser to test the HTTP connection and by default a web browser also sends a request for favicon.ico. So two requests were actually coming across. Thank you to @Inuyasha for suggesting I check things out with Wireshark.