Your Comments.

• # re: ASP.NET (1.x and 2.x) maxRequestLength suckyness...

  What also sucks is that you HAVE to put this size limit into the Webconfig file and we try to always AVOID webconfig.
  
  that would be a nice improvement for ASP.Net 3......

  Left by Steven at 4/4/2006 11:22 PM
• # re: ASP.NET (1.x and 2.x) maxRequestLength suckyness...

  There might be a way to handle this exception:
  
  1. Create a global.asax file. If you're using Visual Studio 2005 it will set up a number of common subroutines for you. You need to use Sub Application_Error. Your code should look something like this:
  
  <script runat="server">
  Sub Application_Error(ByVal sender As Object, ByVal e As EventArgs)
  Dim currentException As Exception
  currentException = Server.GetLastError.GetBaseException()
  Response.Redirect("/error.aspx?Err=" & Server.UrlEncode(currentException.Message))
  End Sub
  </script>
  
  The application_Error sub fires as a last resort, in other words, when you haven't explicitly handled the exception anywhere else in your code.
  
  2. You can now create an error.aspx that displays the exception message (from the querystring). For this exception the message is "Maximum request length exceeded". You could also test for the message and give users more information on the error.
  

  Left by Grant Castner at 4/21/2006 10:12 PM