When uploading a 42MB file through my ASP.NET Web Application, an issue is occuring where the following errors appear depending on the browser being used:
Google Chrome:
Oops! This link appears to be broken
FireFox:
XML Parsing Error: no element found
Internet Explorer
The webpage cannot be found
I don't believe this is an issue with file size restrictions as I have the following in my web.config:
<httpRuntime maxRequestLength="409600" executionTimeout="9000" />
This is working fine on our development server (IIS6), but not on the live server (IIS7)
Why is this and how can I prevent this from happening?
IIS7 doesn't seem to read:
<httpRuntime maxRequestLength="409600" />
The IIS7 alternative seems to be:
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="209715200"></requestLimits>
</requestFiltering>
</security>
</system.webServer>
Related
I am working on a webApplication that uses telerik. One of the telerik popups up upon closing (by clicking X on top right) gives HTTP Error 403.14 - Forbidden.
This happens only on IE. works fine on chrome and firefox.
My web config have below tags that are required to eliminate this error
runAllManagedModulesForAllRequests="false"
<system.webServer>
<defaultDocument>
<files>
<clear/>
<add value="Default.aspx"/>
</files>
</defaultDocument>
</system.webServer>
Help is much appreciated. Thanks!
If you are using multiple projects in your solution then select one of project and set option 'set up as startup project' then compile and rebuild your project.
Also try to add code below in your web.config file.
<system.webServer>
<directoryBrowse enabled="true" />
</system.webServer>
Im building a MVC 5 app, where users can upload images. I ran into the filsize cap of 4mb. the solution I can read is to add this to web.config:
<system.web>
<httpRuntime executionTimeout="240" maxRequestLength="20480" />
</system.web>
but when doing so, the site crashes with an configuration error:
The requested page cannot be accessed because the related configuration data for the page is invalid.
Removing the line and the site is running again.
Is there an alternative or workarround?
For IIS7 or later, add this line to webconfig
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="52428800" /> <!--50MB-->
</requestFiltering>
</security>
</system.webServer>
Or open IIS GUI
Hi I am new to IIS and Asp Net programming. I am working with IIs 8.0 and I am wondering why the requestFiltering method for denyUrlSequences is not working for ms-dos device names like /AUX.
Here is my code in the Web.config
<system.webServer>
<security>
<requestFiltering>
<!-- block /CFIDE -->
<denyUrlSequences>
<add sequence="/AUX"/>
</denyUrlSequences>
</requestFiltering>
</security>
</system.webServer>
this works if the but it does not work for the case with AUX. It just gives server errors not Http 404.5. Is there any other configurations I must do to get this to work?
THank you!
i just moved from my old host to Godaddy, which seems to be a worst web host with no support.
i moved my asp website (written in classic asp) to the new godaddy windows hosting. but when i run the site i get the below error
HTTP/1.1 New Application Failed
this site worked perfectly with my previous host.
below is what i have in my web.config file
<?xml version="1.0"?>
<configuration>
<system.webServer>
<httpErrors errorMode="Detailed" />
<asp scriptErrorSentToBrowser="true"/>
</system.webServer>
<system.web>
<customErrors mode="Off"/>
<compilation debug="true"/>
</system.web>
</configuration>
can someone tell me why am i getting that error and how can i fix it?
any help will be appreciated.
I had the same issue moving a website from one hosting account (classic windows) to another (plesk), both on GoDaddy. After much headache troubleshooting, I managed to fix it by removing the whole <asp> tag from the web.config file;
<!-- <asp scriptErrorSentToBrowser="true"/> -->
IIS 8 (only option in plesk) does not support this option altogether and configuring detailed error messaging is done differently using:
<httpErrors errorMode="Detailed" existingResponse="PassThrough" />
You can find further instructions on this GoDaddy support page
I just encountered the same error this morning after renaming some Websites in IIS. A restart of IIS got my sites up and running again in seconds. Presumably the .config files are read on startup and 'likely' the cause of this error for me.
I have built a video site using Webmatrix 2 but when I try and upload a min of two videos .webm and .mp4 (in this case both files add up to about 34mb) I get this error...
"The request filtering module is configured to deny a request that exceeds the request content length."
The site is running locally on my machine with an instance of IIS 8. I have tried adding Maxrequest and executeTimeout without any luck.
web.config <httpRuntime maxRequestLength="2000000" executionTimeout="600" />
Any help would be appreciated
For anyone interested I applied the following that sorted it out.
Read this article that explains it well:
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="524288000"/>
</requestFiltering>
</security>
</system.webServer>