MessageHandlers associated with an IHttpRoute do not currently trace, but they should.
Fixing this issue entails making the TraceManager wrap tracing message handlers around the HttpMessageHandlers for each route, the same way it does for HttpConfiguration.MessageHandlers.
Repro:
1. Create an app like Henrik's blog at http://blogs.msdn.com/b/henrikn/archive/2012/05/03/asp-net-web-api-updates-may-3.aspx that adds a per-route message handler
2. Enable tracing (any trace writer)
3. Run app and observe that a request invoking that route does not trace anything done by that per-route messagehandler.
The main HttpConfiguration MessageHandlers do trace. Only the per-route messagehandlers do not.
Fixing this issue entails making the TraceManager wrap tracing message handlers around the HttpMessageHandlers for each route, the same way it does for HttpConfiguration.MessageHandlers.
Repro:
1. Create an app like Henrik's blog at http://blogs.msdn.com/b/henrikn/archive/2012/05/03/asp-net-web-api-updates-may-3.aspx that adds a per-route message handler
2. Enable tracing (any trace writer)
3. Run app and observe that a request invoking that route does not trace anything done by that per-route messagehandler.
The main HttpConfiguration MessageHandlers do trace. Only the per-route messagehandlers do not.