404 results when application Content-Type / x-www-form-urlencoded

I am getting 404 in /mini-profiler-resources/results

and after messing with Fiddler request. I notice that it only returns 404 when Content-Type: application/x-www-form-urlencoded; charset=UTF-8

sent with a request.

Changing or deleting a content type results in a 200 response.

Message returning 404 is fired includes.js

I have installed MiniProfiler handler in my web.config as such:

<handlers> <add name="MiniProfiler" path="mini-profiler-resources/*" verb="*" type="System.Web.Routing.UrlRoutingModule" resourceType="Unspecified" preCondition="integratedMode" /> </handlers>

Any idea why this only returns 404 with the specified content type above?

UPDATE

I have two projects working here and this seems to be causing the 404 issue.

In IIS, I have a website pointing to my web application folder, and an application running inside that pointing to my web API project.

I am trying to record ajax calls to web api but that seems to be causing the problem. If I remove the calls MiniProfiler.Stop()

to the global.asax web API the 404 problem goes away. However MiniProfiler cannot handle ajax requests to API endpoints.

My guess is that I need to store the profiling results in some central location rather than using the default provider. The call Stop

was a premature killing of the MiniProfiler process?