IIS & ASP.NET: when a client disconnects, what happens to the request worker process?
<p><strong>Context:</strong> We run our ASP.NET site behind an AWS load balancer which times requests out after 60 seconds. The first ever request to our site may take longer than this while caches warm up etc. There's obvious improvements we could make to this strategy, but that's beside the point for this question.</p>

<p>Assuming that the connection to our IIS instance is closed after 60 seconds, what happens to the execution of that request, in terms of my code being run? </p>

<p>Does it </p>

<ul>
<li>continue even though there's no one to send the eventual response to?</li>
<li>kill the process - possibly during some disk IO operation?</li>
<li>run for the server's configured timeout value?</li>
<li>do something smarter?</li>
</ul>