Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryLarge DownloadsLarge Downloads
Previous
 
Next
New Post
8/2/2006 12:28 AM
 
You'll have to download the file from W4L and edit it with a text editor (Notepad will work fine) and then re-upload it. You might also need to check with W4L about whether you can make those changes to it. I don't know what policies they have on that type of thing.
 
New Post
8/2/2006 11:39 AM
 

Thanks for your assistance. In looking at the web.config file at W4L, I find the following line:

    <!-- allow large file uploads -->
    <httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192" requestLengthDiskThreshold="8192" />

Obviously, no value for TimeOut in this line or any other line in the file.

So, should I add the TimeOut value to this line - and what should I set it to?

Also, if "maxRequestLength=8192" works for a 4MB file but fails for an 8MB file, what value should I set it to to allow for 40MB files?

Thanks much,

Jeff


Jeff
 
New Post
8/2/2006 1:19 PM
 

I went with these settings and it worked with an 8MB file. Thanks!

<!-- allow large file uploads -->
    <httpRuntime executionTimeout="600" useFullyQualifiedRedirectUrl="true" maxRequestLength="24000" requestLengthDiskThreshold="8192" />

Do I need to do something with DNN to get it to load the new version of web.config? All I did was to download the file, edit it, and re-upload it via FTP.

Thanks.


Jeff
 
New Post
8/2/2006 2:34 PM
 

The .NET worker process recognizes when the .config file has been changed and automatically reloads everything. You may have noticed that after you uploaded the edited web.config your site to longer than normal to load the first time.

 
New Post
8/2/2006 4:52 PM
 

I don't know if anyone else has the same problem I have had with large files or not. In any case, I figured I would post the workaround i am using.

Instead of uploading large files into DNN using the file manager, I use the URL link option to link directly to the file on the server. (Ex. http://localhost/<filepath>/<filename>) This not only allows for really large downloads without changing IIS or .config, but it eliminates upload time into file manager and users can download faster. I would prefer not to use this method, but, hey it works.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryLarge DownloadsLarge Downloads


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out