title: What are the specific behaviours of runAllManagedModulesForAllRequests="false"?
body: <p>Regarding <code>&lt;modules runAllManagedModulesForAllRequests="true"&gt;</code></p>
  
  <p>The MSDN documentation <a href="http://msdn.microsoft.com/en-us/library/ms691427%28v=vs.90%29.aspx#CommunityContent" rel="nofollow">states</a> about the attribute: </p>
  
  <blockquote>
    <p>A read/write boolean value. true if all managed modules are run for every request; otherwise, false. The default is false.  </p>
  </blockquote>
  
  <p>This <a href="http://www.britishdeveloper.co.uk/2010/06/dont-use-modules-runallmanagedmodulesfo.html" rel="nofollow">article</a> describes  a bit more about its "true" value behaviour: </p>
  
  <blockquote>
    <p>This highly recommended fix can cause other problems. These problems come in the form of making all your registered HTTP modules run on every request, not just managed requests (e.g. .aspx). This means modules will run on ever .jpg .gif .css .html .pdf etc.</p>
  </blockquote>
  
  <p>Now about: <em>runAllManagedModulesForAllRequests="<strong>false</strong>"</em> ... </p>
  
  <p>My question -- that the MSDN docs don't seem to get into specifics about --  is how does the false value behave other than just the general description of not running all managed modules for every request?  </p>
  
  <p>For example, does "false" skip some modules yet run the request through a bunch of others; does the request stop on the first module that processes it like a handler, etc.?  And how do unmanaged modules fit into the behaviour? </p>
  
  <p>Overall is there a good guide or description for this behaviour? </p>