I Swear I Didn't Know I Could Do This!

I’m a big fan of HttpModules and HttpHandlers. Hey, I even created a tool to code-gen those for you!

Here’s one gotcha with HttpModules: if you invoke code which relies on HttpContext.Current, it may be null, as in the case of kicking off a timer which lives on its own, separate thread.

I dug into HttpContext with Reflector and noticed that the HttpContext.Current property had a setter. Imagine my surprise when I did the following, and it worked!

private void ScheduleCallback (object state)
{
    // ...
    HttpContext.Current = state as HttpContext;
    // ...
}

I don’t know if I’m violating anything here, but it functions just fine. I’ll take that.

Btw, this post clarifies what that state is.