YAFLogo

netghost
  • netghost
  • 80.6% (Honored)
  • YAF Lover Topic Starter
12 years ago
i get a timeout when i try uploading a file of about 5mb .. "Request Timed out" ...
Sponsor
tha_watcha
  • tha_watcha
  • 100% (Exalted)
  • YAF.NET Project Lead 🤴 YAF Version: 4.0.0 rc 2
12 years ago

i get a timeout when i try uploading a file of about 5mb .. "Request Timed out" ...

Originally Posted by: netghost 

Then simply increase the maxRequestLength Value

<httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="10192" requestLengthDiskThreshold="108192" requestValidationMode="2.0" />

In that case you can upload files about 10 MB

Dr-Hack
  • Dr-Hack
  • 100% (Exalted)
  • YAF All-the-Time
12 years ago
Got Out-posted . .Consider as Obsolete

Very Simple ..

1. Open Google.com

2. Type "Upload Timeout YAF"

3. Press the "I'm Feeling Lucky Button" or Enter.

4. Select the First Result.

5. Read the 2nd Pos t on that Page written by the_watcha.

netghost
  • netghost
  • 80.6% (Honored)
  • YAF Lover Topic Starter
12 years ago
i get a runtime error when i add the http runtime tag to my web.config file
tha_watcha
  • tha_watcha
  • 100% (Exalted)
  • YAF.NET Project Lead 🤴 YAF Version: 4.0.0 rc 2
12 years ago

i get a runtime error when i add the http runtime tag to my web.config file

Originally Posted by: netghost 

Please post the full error message

netghost
  • netghost
  • 80.6% (Honored)
  • YAF Lover Topic Starter
12 years ago

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>
tha_watcha
  • tha_watcha
  • 100% (Exalted)
  • YAF.NET Project Lead 🤴 YAF Version: 4.0.0 rc 2
12 years ago
Please do what the error message says and turn off custom errors to see the real error.

 <customErrors mode="Off"/>
squirrel
12 years ago
You said you get an error when you "ADD" the tag for httpruntime. Look and make sure you don't already have one and make changes to it. You can't have two httpruntime tags in one web.config
If you can't find it using the forum search, try my signature link -- searches this site using Google: Google is my Friend 
netghost
  • netghost
  • 80.6% (Honored)
  • YAF Lover Topic Starter
12 years ago

Server Error in '/' Application.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. 

Parser Error Message: Unrecognized attribute 'requestValidationMode'. Note that attribute names are case-sensitive.

Source Error: 


Line 13: 	</system.net>
Line 14: 	<system.web>
Line 15: 	<httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="10192" requestLengthDiskThreshold="108192" requestValidationMode="2.0" />
Line 16: 		<trace enabled="false"/>
Line 17: 		<xhtmlConformance mode="Transitional"/>

Source File: C:\Inetpub\vhosts\woonick.com\httpdocs\web.config    Line: 15 

error message

squirrel
12 years ago


Server Error in '/' Application.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. 

Parser Error Message: Unrecognized attribute 'requestValidationMode'. Note that attribute names are case-sensitive.

Source Error: 


Line 13: 	</system.net>
Line 14: 	<system.web>
Line 15: 	<httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="10192" requestLengthDiskThreshold="108192" requestValidationMode="2.0" />
Line 16: 		<trace enabled="false"/>
Line 17: 		<xhtmlConformance mode="Transitional"/>

Source File: C:\Inetpub\vhosts\woonick.com\httpdocs\web.config    Line: 15 

error message

Originally Posted by: netghost 

If it's complaining about the "requestValidationMode" parameter, everything I read states that you need to verify that your app is actually running in a .NET 4.0 application pool. That error generally means that the pool is running in 2.0/3.5 mode. If anything, paste the 'bottom' of that error into a reply here. The last line in the error page usually states the '.NET version' of the pool that is running the code that generated the error.


If you can't find it using the forum search, try my signature link -- searches this site using Google: Google is my Friend 
JP
  • JP
  • 100% (Exalted)
  • YAF Leader
12 years ago
As squirrel says, your forum application is probably running in a .Net 2.0 application pool. The web.config backwards compatibility parameter requestValidationMode is not recognized there.

Have had the same issue - Been there, done that...


He who asks a question is a fool for five minutes. He who does not ask a question remains a fool forever. [Old Chinese Proverb]
netghost
  • netghost
  • 80.6% (Honored)
  • YAF Lover Topic Starter
12 years ago
requestValidationMode="2.0"

i removed the above section from the code and it works fine

squirrel
12 years ago
Be aware, if you are running forum version 1.9.6 or higher, you must have .NET 4.0 or you will run into problems. If by removing that value from web.config that pretty much confirms you are running in a .NET 2.0/3.5 pool, which is not right for YAF v1.9.6 (any) and higher.
If you can't find it using the forum search, try my signature link -- searches this site using Google: Google is my Friend