carbocation/interpose — pull request #5 by cryptix (2014-07-27 11:26:16+00:00)
Title: gorilla/context - don't leave old requests in the map

Hi,

after reading [this](https://elithrar.github.io/article/map-string-interface/) article on different context passing techniques I noticed that we had this problem in the examples. From the article:

> The downsides? The global map and its mutexes may result in contention at high loads, and you need to call context.Clear() at the end of every request (i.e. on each handler). Forget to do that (or wrap your top-level server handler) and you'll open yourself up to a memory leak where old requests remain in the map. If you're writing middleware that uses gorilla/context, then you need to make sure your package user imports context calls context.ClearHandler on their handlers/router.