Catching Maximum request length exceeded

Question

I m writing an upload function  and have problems catching  System Web HttpException  Maximum request length exceeded  with files larger than the specified max size in httpRuntimein web config  max size set to 5120   I m using a simple  lt input gt  for the file   The problem is that the exception is thrown before the upload button s click-event  and the exception happens before my code is run  So how do I catch and handle the exception   EDIT  The exception is thrown instantly  so I m pretty sure it s not a timeout issue due to slow connections

User · Answer

One way to do this is to set the maximum size in web.config as has already been stated above e.g.

<system.web>         
    <httpRuntime maxRequestLength="102400" />     
</system.web>

then when you handle the upload event, check the size and if its over a specific amount, you can trap it e.g.

protected void btnUploadImage_OnClick(object sender, EventArgs e)
{
    if (fil.FileBytes.Length > 51200)
    {
         TextBoxMsg.Text = "file size must be less than 50KB";
    }
}

User · Answer

Hi solution mentioned by Damien McGivern  Works on IIS6 only   It does not work on IIS7 and ASP NET Development Server  I get page displaying  404 - File or directory not found    Any ideas   EDIT   Got it    This solution still doesn t work on ASP NET Development Server  but I got the reason why it was not working on IIS7 in my case   The reason is IIS7 has a built-in request scanning which imposes an upload file cap which defaults to 30000000 bytes  which is slightly less that 30MB    And I was trying to upload file of size 100 MB to test the solution mentioned by Damien McGivern  with maxRequestLength  10240  i e  10MB in web config   Now  If I upload the file of size   10MB and  lt  30 MB then the page is redirected to the specified error page  But if the file size is   30MB then it show the ugly built-in error page displaying  404 - File or directory not found    So  to avoid this  you have to increase the max  allowed request content length for your website in IIS7  That can be done using following command   appcmd set config  SiteName  -section requestFiltering -requestLimits maxAllowedContentLength 209715200 -commitpath apphost   I have set the max  content length to 200MB   After doing this setting  the page is succssfully redirected to my error page when I try to upload file of 100MB  Refer  http   weblogs asp net jgalloway archive 2008 01 08 large-file-uploads-in-asp-net aspx for more details

User · Answer

If you are wanting a client side validation also so you get less of a need to throw exceptions you could try to implement client side file size validation   Note  This only works in browsers that support HTML5  http   www html5rocks com en tutorials file dndfiles          lt form id  FormID  action  post  name  FormID  gt       lt input id  target  name  target  class  target  type  file    gt   lt  form gt    lt script src  http   ajax googleapis com ajax libs jquery 1 6 1 jquery min js  type  text javascript  gt  lt  script gt    lt script type  text javascript  language  javascript  gt           target   change function               if  typeof FileReader      undefined                 var size   document getElementById  target   files 0  size                 check file size              if  size  gt  100000                       this  val                                          lt  script gt

User · Answer

Here s an alternative way  that does not involve any  hacks   but requires ASP NET 4 0 or later     Global asax private void Application Error object sender  EventArgs e        var ex   Server GetLastError        var httpException   ex as HttpException    ex InnerException as HttpException      if httpException    null  return       if httpException WebEventCode    WebEventCodes RuntimeErrorPostTooLarge                  handle the error         Response Write  Sorry  file is too big      show this message for instance

User · Answer

How about catch it at EndRequest event   protected void Application EndRequest object sender  EventArgs e                HttpRequest request   HttpContext Current Request          HttpResponse response   HttpContext Current Response          if   request HttpMethod     POST    amp  amp               response StatusCode    404  amp  amp  response SubStatusCode    13                            Clear the response header but do not clear errors and                transfer back to requesting page to handle error             response ClearHeaders                HttpContext Current Server Transfer request AppRelativeCurrentExecutionFilePath

User · Answer

You can solve this by increasing the maximum request length and execution time out  in your web config   -Please Clarify the maximum execution time out grater then 1200    lt  xml version  1 0  encoding  utf-8   gt   lt configuration gt   lt system web gt   lt httpRuntime maxRequestLength  102400  executionTimeout  1200    gt   lt  system web gt   lt  configuration gt

User · Answer

As you probably know  the maximum request length is configured in TWO places    maxRequestLength - controlled at the ASP NET app level maxAllowedContentLength - under  lt system webServer gt   controlled at the IIS level   The first case is covered by other answers to this question   To catch THE SECOND ONE you need to do this in global asax   protected void Application EndRequest object sender  EventArgs e          check for the  file is too big  exception if thrown at the IIS level     if  Response StatusCode    404  amp  amp  Response SubStatusCode    13                Response Write  Too big a file      just an example         Response End

User · Answer

In IIS 7 and beyond   web config file    lt system webServer gt     lt security  gt       lt requestFiltering gt         lt requestLimits maxAllowedContentLength   Size In Bytes     gt       lt  requestFiltering gt     lt  security gt   lt  system webServer gt    You can then check in code behind  like so   If FileUpload1 PostedFile ContentLength  gt  2097152 Then    2097152   2 Mb      Exceeded the 2 Mb limit     Do something End If   Just make sure the  Size In Bytes  in the web config is greater than the size of the file you wish to upload then you won t get the 404 error  You can then check the file size in code behind using the ContentLength which would be much better

User · Answer

I m using a FileUpload control and client side script to check the file size   HTML  note the OnClientClick - executed before OnClick    lt asp FileUpload ID  quot FileUploader quot  runat  quot server quot    gt   lt br   gt   lt asp Button ID  quot btnUpload quot  Text  quot Upload quot  runat  quot server quot  OnClientClick  quot return checkFileSize   quot  OnClick  quot UploadFile quot    gt   lt br   gt   lt asp Label ID  quot lblMessage quot  runat  quot server quot  CssClass  quot lblMessage quot  gt  lt  asp Label gt   Then the script  note the  return false  if the size is too big  this is to cancel the OnClick   function checkFileSize          var input   document getElementById  quot FileUploader quot        var lbl   document getElementById  quot lblMessage quot        if  input files 0  size  lt  4194304                lbl className    quot lblMessage quot           lbl innerText    quot File was uploaded quot             else               lbl className    quot lblError quot           lbl innerText    quot Your file cannot be uploaded because it is too big  4 MB max   quot           return false

User · Answer

It can be checked via           var httpException   ex as HttpException          if  httpException    null                        if  httpException WebEventCode    System Web Management WebEventCodes RuntimeErrorPostTooLarge                                   Request too large                  return

User · Answer

You can solve this by increasing the maximum request length in your web config    lt  xml version  1 0  encoding  utf-8   gt   lt configuration gt       lt system web gt           lt httpRuntime maxRequestLength  102400    gt       lt  system web gt   lt  configuration gt    The example above is for a 100Mb limit

User · Answer

There is no easy way to catch such exception unfortunately  What I do is either override the OnError method at the page level or the Application Error in global asax  then check if it was a Max Request failure and  if so  transfer to an error page   protected override void OnError EventArgs e          private void Application Error object sender  EventArgs e        if  GlobalHelper IsMaxRequestExceededException this Server GetLastError                   this Server ClearError            this Server Transfer    error UploadTooLarge aspx              It s a hack but the code below works for me  const int TimedOutExceptionCode   -2147467259  public static bool IsMaxRequestExceededException Exception e           unhandled errors   caught at global ascx level        http exception   caught at page level      Exception main      var unhandled   e as HttpUnhandledException       if  unhandled    null  amp  amp  unhandled ErrorCode    TimedOutExceptionCode                main   unhandled InnerException            else               main   e              var http   main as HttpException       if  http    null  amp  amp  http ErrorCode    TimedOutExceptionCode                   hack  no real method of identifying if the error is max request exceeded as             it is treated as a timeout exception         if  http StackTrace Contains  GetEntireRawContent                             MAX REQUEST HAS BEEN EXCEEDED             return true                       return false

User · Answer

A solution that works with IIS7 and upwards  Display custom error page when file upload exceeds allowed size in ASP NET MVC

User · Answer

After tag    lt security gt        lt requestFiltering gt            lt requestLimits maxAllowedContentLength  4500000    gt        lt  requestFiltering gt   lt  security gt    add the following tag    lt httpErrors errorMode  Custom  existingResponse  Replace  gt     lt remove statusCode  404  subStatusCode  13    gt     lt error statusCode  404  subStatusCode  13  prefixLanguageFilePath    path  http   localhost ErrorPage aspx  responseMode  Redirect    gt   lt  httpErrors gt    you can add the Url to the error page

User · Answer

As GateKiller said you need to change the maxRequestLength  You may also need to change the executionTimeout in case the upload speed is too slow  Note that you don t want either of these settings to be too big otherwise you ll be open to DOS attacks   The default for the executionTimeout is 360 seconds or 6 minutes   You can change the maxRequestLength and executionTimeout with the httpRuntime Element    lt  xml version  1 0  encoding  utf-8   gt   lt configuration gt       lt system web gt           lt httpRuntime maxRequestLength  102400  executionTimeout  1200    gt       lt  system web gt   lt  configuration gt    EDIT   If you want to handle the exception regardless then as has been stated already you ll need to handle it in Global asax  Here s a link to a code example

[c#] Catching "Maximum request length exceeded"

Examples related to c#

Examples related to asp.net

Examples related to httpexception