Using ASP.NET Web API, my ExecutionContext isn't flowing in async actions
I'm having difficulty understanding the mechanics behind ExecutionContext. From what I've read online, context-sensitive items such as security (Thread Principal), culture, etc, should flow across asynchronous threads within the bounds of an execution unit of work. I'm encountering very confusing and potentially dangerous bugs though. I'm noticing my thread's CurrentPrincipal is getting lost across async execution. Here is an example ASP.NET Web API scenario: First, let's setup a simple Web API configuration with two delegating handlers for testing purposes. All they do is write out debug