| Groups | Blog | Home |
asp.net : How to intercept error when httpRuntime maxRequestLength is exceded.
I have an application where users need to upload images and in my web.config
file I have a setting like this: <httpRuntime maxRequestLength="512" /> Which restricts image larger than 500k from being uploaded. I'm also using the HtmlInputFile control to do the uploading. My problem is that when the user's file size exceeds 512k, the page immediately redirects to the "The page cannot be displayed" error page which is very confusing. The use will think that their image is corrupt, or the website has a nasty bug in it. The way this should be handled is instead of showing the nasty "The page cannot be displayed" page, show a friendly page telling the user that they exceeded the file limit and to upload a smaller image. Is there a way to intercept this and do a redirect? and if not, is there any other way to handle this elegantly? -- moondaddy@nospam.com
You should be able to handle this in the Application_Error event in the
Global.asax. The code below just shows some example code void Application_Error(object sender, EventArgs e) { SomeStringVar = .Server.GetLastError.Message(); Server.Transfer("Errors.aspx") Server.ClearError() } You could also have a web.config setting that captures that particular Http error number and redirects accordingly. Something like :- <configuration> <system.web> <customErrors defaultRedirect="GenericError.htm" mode="RemoteOnly"> <error statusCode="500" redirect="InternalError.htm"/> </customErrors> </system.web> </configuration> You could change (or add another entry) to the '500' for whatever error code you want. -- - Paul Glavich Microsoft MVP - ASP.NET [quoted text, click to view] "moondaddy" <moondaddy@nospam.com> wrote in message news:O%23lzXrXYEHA.3988@tk2msftngp13.phx.gbl... > I have an application where users need to upload images and in my web.config > file I have a setting like this: > > <httpRuntime maxRequestLength="512" /> > > Which restricts image larger than 500k from being uploaded. I'm also using > the HtmlInputFile control to do the uploading. My problem is that when the > user's file size exceeds 512k, the page immediately redirects to the "The > page cannot be displayed" error page which is very confusing. The use will > think that their image is corrupt, or the website has a nasty bug in it. > The way this should be handled is instead of showing the nasty "The page > cannot be displayed" page, show a friendly page telling the user that they > exceeded the file limit and to upload a smaller image. > > Is there a way to intercept this and do a redirect? and if not, is there > any other way to handle this elegantly? > > -- > moondaddy@nospam.com > >
Thanks Paul. I have a few questions/comments. 1) I pasted the error page
text below so you can see the error coming back. There is no error number so I can't use your example using the web.config file. and 2) I put a break in the global.asax code behind to step through the code and study the error message, but the Application_Error event doesnt fire so this must not be an application error Sub Application_Error(ByVal sender As Object, ByVal e As EventArgs) Dim str As String = Server.GetLastError.Message Log(str , EventLogEntryType.Error) End Sub All I know is that the webconfig file's line <httpRuntime maxRequestLength="512" /> tells asp.net what the constraint is. Any other ideas on how to trap this error and handle it? The page cannot be displayed The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings. -------------------------------------------------------------------------- Please try the following: a.. Click the Refresh button, or try again later. b.. If you typed the page address in the Address bar, make sure that it is spelled correctly. c.. To check your connection settings, click the Tools menu, and then click Internet Options. On the Connections tab, click Settings. The settings should match those provided by your local area network (LAN) administrator or Internet service provider (ISP). d.. If your Network Administrator has enabled it, Microsoft Windows can examine your network and automatically discover network connection settings. If you would like Windows to try and discover them, click Detect Network Settings e.. Some sites require 128-bit connection security. Click the Help menu and then click About Internet Explorer to determine what strength security you have installed. f.. If you are trying to reach a secure site, make sure your Security settings can support it. Click the Tools menu, and then click Internet Options. On the Advanced tab, scroll to the Security section and check settings for SSL 2.0, SSL 3.0, TLS 1.0, PCT 1.0. g.. Click the Back button to try another link. Cannot find server or DNS Error Internet Explorer -- moondaddy@nospam.com "Paul Glavich [MVP - ASP.NET]" <glav@aspalliance.com-NOSPAM> wrote in message news:uKNwkQZYEHA.2812@TK2MSFTNGP11.phx.gbl... [quoted text, click to view] > You should be able to handle this in the Application_Error event in the > Global.asax. The code below just shows some example code > > void Application_Error(object sender, EventArgs e) > { > SomeStringVar = .Server.GetLastError.Message(); > Server.Transfer("Errors.aspx") > Server.ClearError() > } > > You could also have a web.config setting that captures that particular Http > error number and redirects accordingly. Something like :- > <configuration> > <system.web> > <customErrors defaultRedirect="GenericError.htm" > mode="RemoteOnly"> > <error statusCode="500" > redirect="InternalError.htm"/> > </customErrors> > </system.web> > </configuration> > > You could change (or add another entry) to the '500' for whatever error code > you want. > > > > -- > - Paul Glavich > Microsoft MVP - ASP.NET > > > "moondaddy" <moondaddy@nospam.com> wrote in message > news:O%23lzXrXYEHA.3988@tk2msftngp13.phx.gbl... > > I have an application where users need to upload images and in my > web.config > > file I have a setting like this: > > > > <httpRuntime maxRequestLength="512" /> > > > > Which restricts image larger than 500k from being uploaded. I'm also > using > > the HtmlInputFile control to do the uploading. My problem is that when > the > > user's file size exceeds 512k, the page immediately redirects to the "The > > page cannot be displayed" error page which is very confusing. The use > will > > think that their image is corrupt, or the website has a nasty bug in it. > > The way this should be handled is instead of showing the nasty "The page > > cannot be displayed" page, show a friendly page telling the user that they > > exceeded the file limit and to upload a smaller image. > > > > Is there a way to intercept this and do a redirect? and if not, is there > > any other way to handle this elegantly? > > > > -- > > moondaddy@nospam.com > > > > > >
Hello,
I think Paul's suggestion should work. I put following code in Application_Error, and it worked: If Request.TotalBytes > MaxValue Then Server.ClearError() Response.Clear() Response.Write "The file is too large" End If
Hmmm, I tried your code below and I get the same result as before, I get the
"The page cannot be displayed" page and it seems as though the Application_Error event isn't firing. The page is actually a user control sitting on a aspx page and the aspx page inherits from a base page. I don't know if this would cause the event to not fire. I put some breaks in the global.asax and I saw the code execute on the Application_BeginRequest event, but it clearly isn't hitting the Application_Error event. I also put a watch on the Response object in the Application_BeginRequest event and saw the there was no value for TotalBytes. below is what was listed in the watch window for TotalBytes" TotalBytes <error: an exception of type: {System.Web.HttpException} occurred> Integer Any other ideas? -- moondaddy@nospam.com [quoted text, click to view] "[MSFT]" <lukezhan@online.microsoft.com> wrote in message news:gjS9SH$YEHA.1580@cpmsftngxa06.phx.gbl... > Hello, > > I think Paul's suggestion should work. I put following code in > Application_Error, and it worked: > > If Request.TotalBytes > MaxValue Then > > Server.ClearError() > > Response.Clear() > > Response.Write "The file is too large" > > End If >
Hmmm, I tried your code below and I get the same result as before, I get the
"The page cannot be displayed" page and it seems as though the Application_Error event isn't firing. The page is actually a user control sitting on a aspx page and the aspx page inherits from a base page. I don't know if this would cause the event to not fire. I put some breaks in the global.asax and I saw the code execute on the Application_BeginRequest event, but it clearly isn't hitting the Application_Error event. I also put a watch on the Response object in the Application_BeginRequest event and saw the there was no value for TotalBytes. below is what was listed in the watch window for TotalBytes" TotalBytes <error: an exception of type: {System.Web.HttpException} occurred> Integer Any other ideas? -- moondaddy@nospam.com [quoted text, click to view] "[MSFT]" <lukezhan@online.microsoft.com> wrote in message news:gjS9SH$YEHA.1580@cpmsftngxa06.phx.gbl... > Hello, > > I think Paul's suggestion should work. I put following code in > Application_Error, and it worked: > > If Request.TotalBytes > MaxValue Then > > Server.ClearError() > > Response.Clear() > > Response.Write "The file is too large" > > End If >
Hello,
Here is the web form code I use to test, you may test them on your server to see if they can work: <form id="Form1" method="post" enctype="multipart/form-data" action="WebForm1.aspx" runat="server"> <INPUT id="oFile" type="file" runat="server" NAME="oFile"> <br> <asp:button id="btnUpload" type="submit" text="Upload" runat="server"></asp:button> <asp:Panel ID="frmConfirmation" Visible="False" Runat="server"> <asp:Label id="lblUploadResult" Runat="server"></asp:Label> </asp:Panel> </form> Private Sub btnUpload_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnUpload.Click Dim strFileName As String Dim strFilePath As String Dim strFolder As String strFolder = "C:\Test\" 'Get the name of the file that is posted. strFileName = oFile.PostedFile.FileName strFileName = Path.GetFileName(strFileName) 'Create the directory if it does not exist. If (Not Directory.Exists(strFolder)) Then Directory.CreateDirectory(strFolder) End If 'Save the uploaded file to the server. strFilePath = strFolder & strFileName If File.Exists(strFilePath) Then lblUploadResult.Text = strFileName & " already exists on the server!" Else oFile.PostedFile.SaveAs(strFilePath) lblUploadResult.Text = strFileName & " has been successfully uploaded." End If 'Display the result of the upload. frmConfirmation.Visible = True End Sub The problem may be related the web control you use. Therefore, we may begin with a basic web form for test. Luke
hey, this is my suggestion. so simple. i think u have to handle this with javascript. in file upload control, u can check for the file size before send t the server. if it is large, give an error. if it is in limit, send t the server. if u need to get the size from the server, u have to add a hidden fiel and set the max value from the web config in the page_load event. tell if it worked. regards, Charit - Charit ----------------------------------------------------------------------- Posted via http://www.codecomments.co -----------------------------------------------------------------------
If my posted file is bigger than maxRequest in httpRuntime i can trap i in Application_Error but the redirect to an error page doesn't works an the process die... I obtain an outpage like classic Cannot find server.... I didn't find a way to redirect user to an error page... You suggest to use js client-side to check file size... but j client-side cannot do it ... can you explain your idea in a block j code?? [quoted text, click to view] Charith wrote: > *hey, this is my suggestion. > > so simple. > i think u have to handle this with javascript. > > in file upload control, u can check for the file size before send t > the server. if it is large, give an error. if it is in limit, send t > the server. > > if u need to get the size from the server, u have to add a hidde > field and set the max value from the web config in the page_loa > event. > > tell if it worked. > > regards, > Charith - atar ----------------------------------------------------------------------- Posted via http://www.codecomments.co -----------------------------------------------------------------------
just check on this, i didnt try. [url]http://www.experts-exchange.com/Web/Web_Languages/JavaScript/Q_20573809.html[/url - Charit ----------------------------------------------------------------------- Posted via http://www.codecomments.co -----------------------------------------------------------------------
[url]http://www.codeproject.com/useritems/FileSelectAndUploadDialog.asp[/url - Charit ----------------------------------------------------------------------- Posted via http://www.codecomments.co -----------------------------------------------------------------------
My pages inherit from a base page so I don't have access to writing
attributes to the form element. You used 2 attributes that I've never used before: enctype and action. Why are you using these and would they have any effect on how errors are trapped in the global.asax? I'm still putting break points on the Application_Error event and also the Global_Error event but these events aren't executing. Can you offer any more advise on how to trap this error so I can redirect to a page with a message to the user? (btw: all of this code is running form a user control which contains all the content for the page, and the page inherits from a base page) The solution mentioned Charith in this thread looks like a good solution, but I'm reluctant to use such JavaScript on the client due to possible problems with downward browsers. Can anyone recommend some proven JavaScript for this? -- moondaddy@nospam.com [quoted text, click to view] "[MSFT]" <lukezhan@online.microsoft.com> wrote in message news:SesAZxVZEHA.1008@cpmsftngxa06.phx.gbl... > Hello, > > Here is the web form code I use to test, you may test them on your server > to see if they can work: > > <form id="Form1" method="post" enctype="multipart/form-data" > action="WebForm1.aspx" runat="server"> > > <INPUT id="oFile" type="file" runat="server" > NAME="oFile"> > > <br> > > <asp:button id="btnUpload" type="submit" > text="Upload" runat="server"></asp:button> > > <asp:Panel ID="frmConfirmation" Visible="False" > Runat="server"> > > <asp:Label id="lblUploadResult" > Runat="server"></asp:Label> > > </asp:Panel> > > </form> > > > > > > Private Sub btnUpload_Click(ByVal sender As System.Object, ByVal e As > System.EventArgs) Handles btnUpload.Click > > Dim strFileName As String > > Dim strFilePath As String > > Dim strFolder As String > > > > strFolder = "C:\Test\" > > > > 'Get the name of the file that is posted. > > strFileName = oFile.PostedFile.FileName > > strFileName = Path.GetFileName(strFileName) > > > > 'Create the directory if it does not exist. > > If (Not Directory.Exists(strFolder)) Then > > Directory.CreateDirectory(strFolder) > > End If > > > > 'Save the uploaded file to the server. > > strFilePath = strFolder & strFileName > > > > If File.Exists(strFilePath) Then > > lblUploadResult.Text = strFileName & " already exists on the > server!" > > Else > > oFile.PostedFile.SaveAs(strFilePath) > > lblUploadResult.Text = strFileName & " has been successfully > uploaded." > > End If > > > > 'Display the result of the upload. > > frmConfirmation.Visible = True > > > > End Sub > > > The problem may be related the web control you use. Therefore, we may begin > with a basic web form for test. > > Luke >
I forgot to mention, I also have this setting in my webconfig:
<customErrors mode="Off"/> for testing. could this have any effect on how the Application_Error event fires? -- moondaddy@nospam.com [quoted text, click to view] "moondaddy" <moondaddy@nospam.com> wrote in message news:%23CDNdYcaEHA.2844@TK2MSFTNGP12.phx.gbl... > My pages inherit from a base page so I don't have access to writing > attributes to the form element. You used 2 attributes that I've never used > before: enctype and action. Why are you using these and would they have > any effect on how errors are trapped in the global.asax? I'm still putting > break points on the Application_Error event and also the Global_Error event > but these events aren't executing. Can you offer any more advise on how to > trap this error so I can redirect to a page with a message to the user? > (btw: all of this code is running form a user control which contains all > the content for the page, and the page inherits from a base page) > > The solution mentioned Charith in this thread looks like a good solution, > but I'm reluctant to use such JavaScript on the client due to possible > problems with downward browsers. Can anyone recommend some proven > JavaScript for this? > > -- > moondaddy@nospam.com > "[MSFT]" <lukezhan@online.microsoft.com> wrote in message > news:SesAZxVZEHA.1008@cpmsftngxa06.phx.gbl... > > Hello, > > > > Here is the web form code I use to test, you may test them on your server > > to see if they can work: > > > > <form id="Form1" method="post" enctype="multipart/form-data" > > action="WebForm1.aspx" runat="server"> > > > > <INPUT id="oFile" type="file" runat="server" > > NAME="oFile"> > > > > <br> > > > > <asp:button id="btnUpload" type="submit" > > text="Upload" runat="server"></asp:button> > > > > <asp:Panel ID="frmConfirmation" > Visible="False" > > Runat="server"> > > > > <asp:Label id="lblUploadResult" > > Runat="server"></asp:Label> > > > > </asp:Panel> > > > > </form> > > > > > > > > > > > > Private Sub btnUpload_Click(ByVal sender As System.Object, ByVal e As > > System.EventArgs) Handles btnUpload.Click > > > > Dim strFileName As String > > > > Dim strFilePath As String > > > > Dim strFolder As String > > > > > > > > strFolder = "C:\Test\" > > > > > > > > 'Get the name of the file that is posted. > > > > strFileName = oFile.PostedFile.FileName > > > > strFileName = Path.GetFileName(strFileName) > > > > > > > > 'Create the directory if it does not exist. > > > > If (Not Directory.Exists(strFolder)) Then > > > > Directory.CreateDirectory(strFolder) > > > > End If > > > > > > > > 'Save the uploaded file to the server. > > > > strFilePath = strFolder & strFileName > > > > > > > > If File.Exists(strFilePath) Then > > > > lblUploadResult.Text = strFileName & " already exists on the > > server!" > > > > Else > > > > oFile.PostedFile.SaveAs(strFilePath) > > > > lblUploadResult.Text = strFileName & " has been successfully > > uploaded." > > > > End If > > > > > > > > 'Display the result of the upload. > > > > frmConfirmation.Visible = True > > > > > > > > End Sub > > > > > > The problem may be related the web control you use. Therefore, we may > begin > > with a basic web form for test. > > > > Luke > > > >
This element didn't take any effect on application_error.
Luke
OK, so where do I go from here?
-- moondaddy@nospam.com [quoted text, click to view] "[MSFT]" <lukezhan@online.microsoft.com> wrote in message news:0lKFNLjaEHA.2688@cpmsftngxa06.phx.gbl... > This element didn't take any effect on application_error. > > Luke >
Hello,
Form's Action property sets or retrieves the URL to which the form content is sent for processing. EncType property sets or retrieves the Multipurpose Internet Mail Extensions (MIME) encoding for the form. Would you please post your client code for the form and <INPUT> component, so I can know what is going on. Regards, Luke
Check your web.config for Trace element, if the trace element is set to true in web.config or in the page directive than Application_Error won't fire.. Give it a try -RK *** Sent via Developersdex http://www.developersdex.com ***
Unfortunately this does not work. I have tried redirecting in the
application_error event but for this particular exception, it seems that asp.net just ignors everything and redirects to the "can't find server or dns error" page. I have customErrors setup in web.config and that seems to be ignored as well. Is there any way we can get microsoft to give us a definitive explanation on this? Are we basically just stuck displaying an unfriendly page to the user that doesn't give them any clue about what happened? Jesse [quoted text, click to view] "Paul Glavich [MVP - ASP.NET]" wrote:
> You should be able to handle this in the Application_Error event in the > Global.asax. The code below just shows some example code > > void Application_Error(object sender, EventArgs e) > { > SomeStringVar = .Server.GetLastError.Message(); > Server.Transfer("Errors.aspx") > Server.ClearError() > } > > You could also have a web.config setting that captures that particular Http > error number and redirects accordingly. Something like :- > <configuration> > <system.web> > <customErrors defaultRedirect="GenericError.htm" > mode="RemoteOnly"> > <error statusCode="500" > redirect="InternalError.htm"/> > </customErrors> > </system.web> > </configuration> > > You could change (or add another entry) to the '500' for whatever error code > you want. > > > > -- > - Paul Glavich > Microsoft MVP - ASP.NET > > > "moondaddy" <moondaddy@nospam.com> wrote in message > news:O%23lzXrXYEHA.3988@tk2msftngp13.phx.gbl... > > I have an application where users need to upload images and in my > web.config > > file I have a setting like this: > > > > <httpRuntime maxRequestLength="512" /> > > > > Which restricts image larger than 500k from being uploaded. I'm also > using > > the HtmlInputFile control to do the uploading. My problem is that when > the > > user's file size exceeds 512k, the page immediately redirects to the "The > > page cannot be displayed" error page which is very confusing. The use > will > > think that their image is corrupt, or the website has a nasty bug in it. > > The way this should be handled is instead of showing the nasty "The page > > cannot be displayed" page, show a friendly page telling the user that they > > exceeded the file limit and to upload a smaller image. > > > > Is there a way to intercept this and do a redirect? and if not, is there > > any other way to handle this elegantly? > > > > -- > > moondaddy@nospam.com > > > > > >
its a 2 part thing. if the client browser could not contact the server in
the first place then it will throw its on error in the form of server not found / dsn error however as Paul mentioned if the error occurred in your code.. then you could handle it. sometimes the server is busy serving and doesnt respond... at that point if you have your custom errors page then it will redirect it -- Regards, Hermit Dave (http://hdave.blogspot.com) [quoted text, click to view] "Jesse" <Jesse@discussions.microsoft.com> wrote in message news:5BA46BAC-7F8A-4349-8BE2-DE6F4B198CAC@microsoft.com... > Unfortunately this does not work. I have tried redirecting in the > application_error event but for this particular exception, it seems that > asp.net just ignors everything and redirects to the "can't find server or dns > error" page. I have customErrors setup in web.config and that seems to be > ignored as well. > > Is there any way we can get microsoft to give us a definitive explanation on > this? Are we basically just stuck displaying an unfriendly page to the user > that doesn't give them any clue about what happened? > > Jesse > > "Paul Glavich [MVP - ASP.NET]" wrote: > > > You should be able to handle this in the Application_Error event in the > > Global.asax. The code below just shows some example code > > > > void Application_Error(object sender, EventArgs e) > > { > > SomeStringVar = .Server.GetLastError.Message(); > > Server.Transfer("Errors.aspx") > > Server.ClearError() > > } > > > > You could also have a web.config setting that captures that particular Http > > error number and redirects accordingly. Something like :- > > <configuration> > > <system.web> > > <customErrors defaultRedirect="GenericError.htm" > > mode="RemoteOnly"> > > <error statusCode="500" > > redirect="InternalError.htm"/> > > </customErrors> > > </system.web> > > </configuration> > > > > You could change (or add another entry) to the '500' for whatever error code > > you want. > > > > > > > > -- > > - Paul Glavich > > Microsoft MVP - ASP.NET > > > > > > "moondaddy" <moondaddy@nospam.com> wrote in message > > news:O%23lzXrXYEHA.3988@tk2msftngp13.phx.gbl... > > > I have an application where users need to upload images and in my > > web.config > > > file I have a setting like this: > > > > > > <httpRuntime maxRequestLength="512" /> > > > > > > Which restricts image larger than 500k from being uploaded. I'm also > > using > > > the HtmlInputFile control to do the uploading. My problem is that when > > the > > > user's file size exceeds 512k, the page immediately redirects to the "The > > > page cannot be displayed" error page which is very confusing. The use > > will > > > think that their image is corrupt, or the website has a nasty bug in it. > > > The way this should be handled is instead of showing the nasty "The page > > > cannot be displayed" page, show a friendly page telling the user that they > > > exceeded the file limit and to upload a smaller image. > > > > > > Is there a way to intercept this and do a redirect? and if not, is there > > > any other way to handle this elegantly? > > > > > > -- > > > moondaddy@nospam.com > > > > > > > > > > > >
I'm going to have to disagree with you. I have full error handling set up on
my site. Error logging in global.asax and custom error setup in web.config. I even tried to explicity catch the System.Web.HttpException that is thrown by exceeding the maxRequestLength and then redirecting to a friendly page. Still no luck there. The only thing that the redirection causes to happen is that the application_error event now gets fired 3 times. I'll get three errors logged and still end up on the dns error page. Go ahead and test this out by stepping through it with the debugger. I'm getting tired of people saying to catch this problem by checking httpPostedFile.ContentLength. You can't do it. The code will never be hit on your page because the runtime throws the exception. So therefore you would think that you could catch it in global.asax, and you can, but any redirection will not work. Why? That is the question. Don't tell me the that the client can't contact the server in these instances. I'm stepping through it with the debugger man. Why don't you setup a test and then you will see. You'll get hte dns error after the server has been hit. I don't know what you mean by "the client browser could not contact the server". It's obviously hitting the server. Has microsoft actually setup an examlpe of this? I can send a simple example solution to anybody that needs proof. [quoted text, click to view] "Hermit Dave" wrote:
> its a 2 part thing. if the client browser could not contact the server in > the first place then it will throw its on error in the form of server not > found / dsn error > > however as Paul mentioned if the error occurred in your code.. then you > could handle it. sometimes the server is busy serving and doesnt respond... > at that point if you have your custom errors page then it will redirect it > > -- > > Regards, > > Hermit Dave > () > > "Jesse" <Jesse@discussions.microsoft.com> wrote in message > news:5BA46BAC-7F8A-4349-8BE2-DE6F4B198CAC@microsoft.com... > > Unfortunately this does not work. I have tried redirecting in the > > application_error event but for this particular exception, it seems that > > asp.net just ignors everything and redirects to the "can't find server or > dns > > error" page. I have customErrors setup in web.config and that seems to be > > ignored as well. > > > > Is there any way we can get microsoft to give us a definitive explanation > on > > this? Are we basically just stuck displaying an unfriendly page to the > user > > that doesn't give them any clue about what happened? > > > > Jesse > > > > "Paul Glavich [MVP - ASP.NET]" wrote: > > > > > You should be able to handle this in the Application_Error event in the > > > Global.asax. The code below just shows some example code > > > > > > void Application_Error(object sender, EventArgs e) > > > { > > > SomeStringVar = .Server.GetLastError.Message(); > > > Server.Transfer("Errors.aspx") > > > Server.ClearError() > > > } > > > > > > You could also have a web.config setting that captures that particular > Http > > > error number and redirects accordingly. Something like :- > > > <configuration> > > > <system.web> > > > <customErrors defaultRedirect="GenericError.htm" > > > mode="RemoteOnly"> > > > <error statusCode="500" > > > redirect="InternalError.htm"/> > > > </customErrors> > > > </system.web> > > > </configuration> > > > > > > You could change (or add another entry) to the '500' for whatever error > code > > > you want. > > > > > > > > > > > > -- > > > - Paul Glavich > > > Microsoft MVP - ASP.NET > > > > > > > > > "moondaddy" <moondaddy@nospam.com> wrote in message > > > news:O%23lzXrXYEHA.3988@tk2msftngp13.phx.gbl... > > > > I have an application where users need to upload images and in my > > > web.config > > > > file I have a setting like this: > > > > > > > > <httpRuntime maxRequestLength="512" /> > > > > > > > > Which restricts image larger than 500k from being uploaded. I'm also > > > using > > > > the HtmlInputFile control to do the uploading. My problem is that > when > > > the > > > > user's file size exceeds 512k, the page immediately redirects to the > "The > > > > page cannot be displayed" error page which is very confusing. The use > > > will > > > > think that their image is corrupt, or the website has a nasty bug in > it. > > > > The way this should be handled is instead of showing the nasty "The > page > > > > cannot be displayed" page, show a friendly page telling the user that > they > > > > exceeded the file limit and to upload a smaller image. > > > > > > > > Is there a way to intercept this and do a redirect? and if not, is > there > > > > any other way to handle this elegantly? > > > > > > > > -- > > > > moondaddy@nospam.com > > > > > > > > > > > > > > > > > > >
okay apologies on my part... i have this problem of not reading the complete
information i never read about HttpPostedFile.. so didnt know that it was the exception that was being thrown due to content length being exceeded. Again - sorry for not reading it fully. i am copying this contents of a discussion we had on MSWebDev.. it has some client side javascript and http module which could be helpful.. and it will also help you understand why you are getting the error and you cant handle it.. --------------------------- <html> <head> <script type="text/javascript"> function CheckAttachment() { var fso = new ActiveXObject("Scripting.FileSystemObject");; if (fso.GetFile(document.all.FileUpload.value).size [quoted text, click to view] > 4000000) {document.all.ErrorMsg.innerHTML = "File to large!"; return false; } return true; } </script> </head> <body> <form enctype="multipart/form-data" method="post" onsubmit="return CheckAttachment()"> File: <input type="file" id="FileUpload" name="FileUpload" /><br /> <input type="Submit" value="Upload" /><br /> <span id="ErrorMsg" name="ErrorMsg"></span> </form> </body> </html> ---------------------------------------------------------------------------- ------ the following code in an HttpModule can read the entire stream and then redirect to an error page. Using buffering means that the entire file won't be sucked into memory in a single shot. However if all you want to do is reject the file for being too large the connection may be tied up for some considerable time before the user gets the error message. This ties in with Jos's comments of using a secondary progress window on the client to potentially recover the broken request scenario: Apologies for the formatting... public void BeginRequest(Object source, EventArgs e) { HttpRequest request = HttpContext.Current.Request; if (request.ContentLength > 4096000) { HttpApplication app = source as HttpApplication; HtttpContext context = app.Context; HttpWorkerRequest wr = (HttpWorkerRequest)(context.GetType().GetProperty ("WorkerRequest", BindingFlags.Instance | BindingFlags.NonPublic).GetValue(context, null)); byte[] buffer; if (wr.HasEntityBody()) { int contentlen = Convert.ToInt32(wr.GetKnownRequestHeader( HttpWorkerRequest.HeaderContentLength)); buffer = wr.GetPreloadedEntityBody(); int received = buffer.Length; int totalrecv = received; if (!wr.IsEntireEntityBodyIsPreloaded()) { buffer = new byte[65535]; while (contentlen - totalrecv >= received) { received = wr.ReadEntityBody(buffer, buffer.Length); totalrecv += received; } received = wr.ReadEntityBody(buffer, contentlen - totalrecv); } } context.Response.Redirect("~/Error.aspx"); } } ---------------------------------------------------------------------------- To redirect the client your server has to send back a response. The redirection is contained in the HTTP headers. To accept a response the client first has to finish requesting the current page. You're rejecting the request itself. The client isn't going to be expecting a response given that it's not even finished telling the server what it wants. ---------------------------------------------------------------------------- -- I can understand why the browser displays the message it does on the client side. What I can't understand is why I can't trap the request, check the content length and reject it myself on the server side. By reject I mean redirecting the user to my own custom error screen if they're attempting to post data that's deemed too large. After installing an HttpModule and adding my own BeginRequest handler, checking the content length and attempting a redirect I would have thought this would prevent the file being uploaded and the transfer taking place. I thought the BeginRequest was the first call within the ASP.NET pipeline allowing me to url map, redirect the user, modify the request etc. -- Regards, Hermit Dave (http://hdave.blogspot.com) [quoted text, click to view] "Jesse" <Jesse@discussions.microsoft.com> wrote in message
news:B8879A40-C914-4C9A-B9EF-8AEDA1A9E86A@microsoft.com... > I'm going to have to disagree with you. I have full error handling set up on > my site. Error logging in global.asax and custom error setup in web.config. > > I even tried to explicity catch the System.Web.HttpException that is thrown > by exceeding the maxRequestLength and then redirecting to a friendly page. > Still no luck there. The only thing that the redirection causes to happen is > that the application_error event now gets fired 3 times. I'll get three > errors logged and still end up on the dns error page. > > Go ahead and test this out by stepping through it with the debugger. I'm > getting tired of people saying to catch this problem by checking > httpPostedFile.ContentLength. You can't do it. The code will never be hit > on your page because the runtime throws the exception. So therefore you > would think that you could catch it in global.asax, and you can, but any > redirection will not work. Why? That is the question. > > Don't tell me the that the client can't contact the server in these > instances. I'm stepping through it with the debugger man. Why don't you > setup a test and then you will see. You'll get hte dns error after the > server has been hit. I don't know what you mean by "the client browser could > not contact the server". It's obviously hitting the server. > > Has microsoft actually setup an examlpe of this? I can send a simple > example solution to anybody that needs proof. > > > > "Hermit Dave" wrote: > > > its a 2 part thing. if the client browser could not contact the server in > > the first place then it will throw its on error in the form of server not > > found / dsn error > > > > however as Paul mentioned if the error occurred in your code.. then you > > could handle it. sometimes the server is busy serving and doesnt respond... > > at that point if you have your custom errors page then it will redirect it > > > > -- > > > > Regards, > > > > Hermit Dave > > () > > > > "Jesse" <Jesse@discussions.microsoft.com> wrote in message > > news:5BA46BAC-7F8A-4349-8BE2-DE6F4B198CAC@microsoft.com... > > > Unfortunately this does not work. I have tried redirecting in the > > > application_error event but for this particular exception, it seems that > > > asp.net just ignors everything and redirects to the "can't find server or > > dns > > > error" page. I have customErrors setup in web.config and that seems to be > > > ignored as well. > > > > > > Is there any way we can get microsoft to give us a definitive explanation > > on > > > this? Are we basically just stuck displaying an unfriendly page to the > > user
was it of any help ?
-- Regards, Hermit Dave (http://hdave.blogspot.com) [quoted text, click to view] "Hermit Dave" <hermitd.REMOVE@CAPS.AND.DOTS.hotmail.com> wrote in message
news:OrK7a4ejEHA.1464@TK2MSFTNGP10.phx.gbl... > okay apologies on my part... i have this problem of not reading the complete > information > > i never read about HttpPostedFile.. so didnt know that it was the exception > that was being thrown due to content length being exceeded. > Again - sorry for not reading it fully. > > i am copying this contents of a discussion we had on MSWebDev.. it has some > client side javascript and http module which could be helpful.. and it will > also help you understand why you are getting the error and you cant handle > it.. > > --------------------------- > > <html> > <head> > <script type="text/javascript"> > function CheckAttachment() > { > var fso = new > ActiveXObject("Scripting.FileSystemObject");; > if (fso.GetFile(document.all.FileUpload.value).size > > 4000000) > { > document.all.ErrorMsg.innerHTML = "File to large!"; > return false; > } > return true; > } > </script> > </head> > <body> > <form enctype="multipart/form-data" method="post" onsubmit="return > CheckAttachment()"> > File: <input type="file" id="FileUpload" name="FileUpload" > /><br /> > <input type="Submit" value="Upload" /><br /> > <span id="ErrorMsg" name="ErrorMsg"></span> > </form> > </body> > </html> > > -------------------------------------------------------------------------- -- > ------ > > the following code in an HttpModule can read the entire stream and then > redirect to an error page. Using buffering means that the entire file won't > be sucked into memory in a single shot. However if all you want to do is > reject the file for being too large the connection may be tied up for some > considerable time before the user gets the error message. This ties in with > Jos's comments of using a secondary progress window on the client to > potentially recover the broken request scenario: > > Apologies for the formatting... > > public void BeginRequest(Object source, EventArgs e) { > HttpRequest request = HttpContext.Current.Request; > if (request.ContentLength > 4096000) > { > HttpApplication app = source as HttpApplication; > HtttpContext context = app.Context; > HttpWorkerRequest wr = > (HttpWorkerRequest)(context.GetType().GetProperty > ("WorkerRequest", BindingFlags.Instance | > BindingFlags.NonPublic).GetValue(context, null)); > byte[] buffer; > if (wr.HasEntityBody()) > { > int contentlen = Convert.ToInt32(wr.GetKnownRequestHeader( > > HttpWorkerRequest.HeaderContentLength)); > buffer = wr.GetPreloadedEntityBody(); > int received = buffer.Length; > int totalrecv = received; > if (!wr.IsEntireEntityBodyIsPreloaded()) > { > buffer = new byte[65535]; > while (contentlen - totalrecv >= received) > { > received = > wr.ReadEntityBody(buffer, > buffer.Length); > totalrecv += received; > } > received = > wr.ReadEntityBody(buffer, contentlen - totalrecv); > } > } > context.Response.Redirect("~/Error.aspx"); > } > } > > -------------------------------------------------------------------------- -- > > To redirect the client your server has to send back a response. The > redirection is contained in the HTTP headers. > > To accept a response the client first has to finish requesting the current > page. > > You're rejecting the request itself. > > The client isn't going to be expecting a response given that it's not even > finished telling the server what it wants. > > > -------------------------------------------------------------------------- -- > -- > > I can understand why the browser displays the message it does on the client > side. > > What I can't understand is why I can't trap the request, check the content > length and reject it myself on the server side. By reject I mean redirecting > the user to my own custom error screen if they're attempting to post data > that's deemed too large. After installing an HttpModule and adding my own > BeginRequest handler, checking the content length and attempting a redirect > I would have thought this would prevent the file being uploaded and the > transfer taking place. I thought the BeginRequest was the first call within > the ASP.NET pipeline allowing me to url map, redirect the user, modify the > request etc. > > > -- > > Regards, > > Hermit Dave > (http://hdave.blogspot.com) > "Jesse" <Jesse@discussions.microsoft.com> wrote in message > news:B8879A40-C914-4C9A-B9EF-8AEDA1A9E86A@microsoft.com... > > I'm going to have to disagree with you. I have full error handling set up > on > > my site. Error logging in global.asax and custom error setup in > web.config. > > > > I even tried to explicity catch the System.Web.HttpException that is > thrown > > by exceeding the maxRequestLength and then redirecting to a friendly page. > > Still no luck there. The only thing that the redirection causes to happen > is > > that the application_error event now gets fired 3 times. I'll get three > > errors logged and still end up on the dns error page. > > > > Go ahead and test this out by stepping through it with the debugger. I'm > > getting tired of people saying to catch this problem by checking > > httpPostedFile.ContentLength. You can't do it. The code will never be > hit > > on your page because the runtime throws the exception. So therefore you > > would think that you could catch it in global.asax, and you can, but any > > redirection will not work. Why? That is the question. > > > > Don't tell me the that the client can't contact the server in these > > instances. I'm stepping through it with the debugger man. Why don't you > > setup a test and then you will see. You'll get hte dns error after the > > server has been hit. I don't know what you mean by "the client browser > could > > not contact the server". It's obviously hitting the server. > > > > Has microsoft actually setup an examlpe of this? I can send a simple > > example solution to anybody that needs proof. > > > > > > > > "Hermit Dave" wrote: > > > > > its a 2 part thing. if the client browser could not contact the server > in > > > the first place then it will throw its on error in the form of server > not > > > found / dsn error > > > > > > however as Paul mentioned if the error occurred in your code.. then you > > > could handle it. sometimes the server is busy serving and doesnt > respond... > > > at that point if you have your custom errors page then it will redirect > it > > > > > > -- > > > > > > Regards, > > > > > > Hermit Dave > > > () > > > > > > "Jesse" <Jesse@discussions.microsoft.com> wrote in message
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |