Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles
(untagged)

An HTTP Module for ASP.NET Error Handling

0.00/5 (No votes)
31 Oct 2006 1  
A simple HTTP module to be used as a "last-resort" error handler for ASP.NET applications. It does not require changes to existing code, and can be "dropped-in" to an already running site.

Introduction

I wrote this HTTP module for a client to plug in an existing site which was having intermittent errors while undergoing integration testing. The client wanted something that could capture the basic error information along with the request query-string/form parameters and write it out. All this needed to be done without modifying the existing code.

Although the existing code did have regular try-catch error handlers in the code-behind files, not all errors were handled properly, and in some cases, the code in the catch block itself was error-prone. Initially, I thought of using a custom error page. However, in view of issues regarding getting the correct context of errors, I decided to use an HTTP module.

The code

The code itself is pretty straightforward.

Step 1 is to wire an event handler for the Error event:

public void Init (HttpApplication app)
{
   app.Error += new System.EventHandler (OnError);
}

Step 2 involves writing the actual event handler to write out the error message and the request form / query-string parameters:

public void OnError (object obj, EventArgs args)
{
   // At this point we have information about the error

   
   HttpContext ctx = HttpContext.Current;
   HttpResponse response = ctx.Response;
   HttpRequest request = ctx.Request;

   Exception exception = ctx.Server.GetLastError();

   response.Write("Your request could not processed. " + 
                  "Please press the back button on" + 
                  " your browser and try again.<br/>");
   response.Write("If the problem persists, please " + 
                  "contact technical support<p/>");
   response.Write("Information below is for " + 
                  "technical support:<p/>");
   
   string errorInfo = "<p/>URL: " + ctx.Request.Url.ToString (); 
  errorInfo += "<p/>Stacktrace:---<br/>" + 
     exception.InnerException.StackTrace.ToString();
  errorInfo += "<p/>Error Message:<br/>" + 
     exception.InnerException.Message;

   //Write out the query string 

   response.Write("Querystring:<p/>");

   for(int i=0;i<request.QueryString.Count;i++)
   {
    response.Write("<br/>" + 
         request.QueryString.Keys[i].ToString() + " :--" + 
         request.QueryString[i].ToString() + "--<br/>");// + nvc.

   }

   //Write out the form collection

   response.Write("<p>---------------" + 
                  "----------<p/>Form:<p/>");

   for(int i=0;i<request.Form.Count;i++)
   {
    response.Write("<br/>" + 
             request.Form.Keys[i].ToString() + 
             " :--" + request.Form[i].ToString() + 
             "--<br/>");// + nvc.

   }

   response.Write("<p>-----------------" + 
                  "--------<p/>ErrorInfo:<p/>");

   response.Write (errorInfo);

   // --------------------------------------------------

   // To let the page finish running we clear the error

   // --------------------------------------------------

   
   ctx.Server.ClearError ();
}

Deployment:

To deploy this HTTP module, simply drop the compiled DLL in the bin folder and make this entry in the web.config to register it:

<system.web>  

    <!-- Add the lines below to register the http module -->    
    <httpModules>
        <add type="MyApps.Utilities.GlobalErrorHandler,
                      GlobalErrorHandler" 
                name="GlobalErrorHandler" />
    </httpModules>  

</system.web>

Download

You can download the complete source code (.cs file), a sample web.config, and the compiled DLL in a single zip file GlobalErrorHandler.zip from the link above.

Further Improvements

This code was really a result of a couple of hours work, so it can obviously be refined. A few changes I am already considering: make the display text dynamic and the overall display more customizable via web.config. In addition, an option to email or log the error messages would be useful. I will be posting updated code in the next few weeks.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here