What could cause ASP.NET's executionTimeout to not be enforced running under IIS?
<p>I'm trying to troubleshoot a problem, but I'm unable to reproduce it locally under IIS because no matter how low I set executionTimeout, the requests never time out.</p>

<p>I've tried setting this via the web.config (, via code (Page.Server.ScriptTimeout = 5;).</p>

<p>I'm running with binaries that were compiled in release mode, and debug=false is set in the compilation element.</p>

<p>FWIW, under Cassini (the standalone development webserver), everything works as expected, running out of the same directory off of the exact same assemblies/config files.</p>

<p>Any ideas on what could be causing this?</p>

<p>EDIT: If it's relevant, the development workstation in question is running Win7/IIS7.</p>

<p>EDIT 2: I'm using reflection to write out HttpContext.Current.Timeout, and in both Cassini and IIS, it's writing out the value I expect, so it seems that it's a matter of the limit being enforced as opposed to being set incorrectly.</p>
