rufanov rufanov - 2 months ago 12
C# Question

How to override default unhandled exception output in Owin?

I've written simple server using Owin Self-hosting and WebApi:

namespace OwinSelfHostingTest
{
using System.Threading;
using System.Web.Http;
using Microsoft.Owin.Hosting;
using Owin;

public class Startup
{
public void Configuration(IAppBuilder builder)
{
var config = new HttpConfiguration();

config.Routes.MapHttpRoute(
"Default",
"{controller}/{id}",
new { id = RouteParameter.Optional }
);

builder.UseWebApi(config);
}
}

public class Server
{
private ManualResetEvent resetEvent = new ManualResetEvent(false);
private Thread thread;

private const string ADDRESS = "http://localhost:9000/";

public void Start()
{
this.thread = new Thread(() =>
{
using (var host = WebApp.Start<Startup>(ADDRESS))
{
resetEvent.WaitOne(Timeout.Infinite, true);
}
});
thread.Start();
}

public void Stop()
{
resetEvent.Set();
}
}

}


When there is exception in controller, then Owin returns XML response like this:

<Error>
<Message>An error has occurred.</Message>
<ExceptionMessage>Attempted to divide by zero.</ExceptionMessage>
<ExceptionType>System.DivideByZeroException</ExceptionType>
<StackTrace>
...
</StackTrace>
</Error>


But i want different output - so how can i override this?

Answer

You do so by creating an OWIN MiddleWare and hooking it into the pipeline:

public class CustomExceptionMiddleware : OwinMiddleware
{
   public CustomExceptionMiddleware(OwinMiddleware next) : base(next)
   {}

   public override async Task Invoke(IOwinContext context)
   {
      try
      {
          await Next.Invoke(context);
      }
      catch(Exception ex)
      {
          // Custom stuff here
      }
   }
 }

And hook it on startup:

public class Startup
{
    public void Configuration(IAppBuilder builder)
    {
        var config = new HttpConfiguration();

        config.Routes.MapHttpRoute(
            "Default",
            "{controller}/{id}",
            new { id = RouteParameter.Optional }
            );

        builder.Use<CustomExceptionMiddleware>().UseWebApi(config);
    }
}

That way any unhandled exception will be caught by your middleware and allow you to customize the output result.

An important thing to note: if the thing being hosted has an exception handling logic of it's own, as WebAPI does, exceptions will not propagate. This handler is meant for any exception which goes by unhandeled by the underlying service being hosted.

Comments