When using MiniProfiler in an application hosted on multiple instances, MiniProfiler receives a 404 when POST is done to /mini-profiler-resources/results.
The reason is because the default implementation of the IStorage provider uses HttpRuntime.Cache. This cache is machine specific, and as a result instance B cannot access the MiniProfiler data saved on instance A.
I thought about submitting this as a pull request to the project, but MiniProfiler would then have to take a dependency on the Azure caching assemblies. I don’t think this is wise, and would bloat Mini Profiler a little bit.
In a perfect world, MiniProfiler would have an ICacheProvider (defaulted to the HttpRuntim.Cache) that we would be able to specify. There could be providers the Azure cache, Memcached, redis, etc…