Apparently this problem has been plagueing programmers for about 10 years. Yet still Microsoft/IIS perhaps has not done anything about it. See this trail from 7 years ago: http://bytes.com/topic/asp-net/answe...error-handling Here 'Mike Moore' says 'that you cannot trap this error to handle it in a custom manner'.
What I have been able to do with a AsyncFileUpload control and the Global.asax is use the Application_Error section. But I can only trap it when I receive the 'Maximum request length exceeded' error. Then I can do a 'Request.Close' and go on with my business. However if I attempt to upload something really huge, say '400MB'. Then the IIS 7.5 server just sits there for a couple of seconds, and then it will give me an annoying popup - 'Server Response Error: Unknown Server Error' (almost like a Javascript alert), then I get a choice, Yes or Cancel. If I choose yes I get a second window with a 404 page. When debugging on the server the Global.asax is never hit.
Indeed in 2012, 7 years after Mike Moore's post, it appears this is still non-trappable and customizable???
Ideally I want to tell the user - "Hey, you picked a file that is way too huge!" Not have them look like they crashed our web-server.