title: How can I handle maxRequestLength exceptions elegantly?
body: <p>In my ASP.NET MVC (v2 if it matters) app, I have a page that allows the user to upload a file.  I've configured the maxRequestLength for my app to allow files up to 25MB.  As a test, I send it a 500MB file which throws the exception: <code>Maximum request length exceeded.</code> (I only know this because ELMAH catches the error and logs it.)</p>
  
  <p>In my web.config, I've set <code>customErrors mode="On"</code> with a <code>defaultRedirect</code>, but the user isn't redirected at all, they don't even get a yellow-screen-of-death.  In Chrome, for example, you'll see the error: <code>Error 101 (net::ERR_CONNECTION_RESET): Unknown error.</code></p>
  
  <p>Is it possible to provide a more elegant user experience for this situation?</p>