Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Uploading a module that's bigger than web.config's max upload sizeUploading a module that's bigger than web.config's max upload size
Previous
 
Next
New Post
12/3/2014 4:59 PM
 
Gift Peddie


Joined: 9/7/2004
Posts: 24
Tony Henrich wrote:
IIS7's default maxRequestLength is 28.6MB (30,000 kbytes). I don't know where the current DNN 12M size came from. Maybe a left over from an earlier version of IIS?

The default maxRequestLength needs to be larger. Modules and extension sizes are getting bigger. Just few days ago a DNN theme creator said he created a theme which is 120M big.  I am pretty sure zipping this with maximum compression, it's still bigger than 12M.

The reason there's a maxRequestLength was to protect IIS from possible disruptive large file uploads or requests. This is a valid protection measure. However the extensions installer and uploader lives in a protected area which is not accessible by the public. The default maxRequestLength can stay as is but add a web.config exception for the extensions page like this. I propose DNN starta shipping with this added config setting:

 Hi Tony,

The IIS Maxlength property can always be adjusted even in IIS 6 it can be increased to 500megs without httphandler, when you get to 1gig in IIS6 then you need httphandler.  What you are seeing is DNN not related to Asp.net.  I don't think adjustment should be moved to page level because you can adjust it in code, two places either Web.config or applicationhost in system 32 which is what is used by IIS7 and up.

The Asp.net 4.5 enhancements comes in only 37megs so theme getting to 120megs is just not practical.  Check the link below for details.

http://stackoverflow.com/questions/68...
 
New Post
12/3/2014 6:23 PM
 
Tony Henrich


Joined: 12/15/2008
Posts: 838
All the code is doing is making the adjustment in web.config through code. it's better to have the setting in web.config so any host can adjust it to their liking without making code changes and recompiling.

"120megs is just not practical". Why not? Zip it and increase the setting in web.config to a size larger than the zip file size and upload. IIS is not going to complain.
 
New Post
12/3/2014 6:50 PM
 
Gift Peddie


Joined: 9/7/2004
Posts: 24
Tony Henrich wrote:
All the code is doing is making the adjustment in web.config through code. it's better to have the setting in web.config so any host can adjust it to their liking without making code changes and recompiling.

"120megs is just not practical". Why not? Zip it and increase the setting in web.config to a size larger than the zip file size and upload. IIS is not going to complain.

 Hi Tony,

I see your point about the setting in the web.config setting but I think DNN is leaving it out because it may require adjustment of the ApplicationHost file at runtime by DNN.

The reason 120megs is not practical is the UI development needs are really fiction created by DNN and the community, the reason DNN install is less than 50megs and the source is less than 100 megs.  In Asp.net 4.5 one aspcontent adds a page with html5 and style so most of what is being developed in DNN UI is none relevant code.
 
New Post
12/3/2014 8:11 PM
 
Tony Henrich


Joined: 12/15/2008
Posts: 838
The size just means it's the sum of sizes of all the files. Not all files are being used or in memory. It means these are the files the software can choose from to do its business. Maybe it has large videos which are only used when the user wants to watch them...
 
 Page 3 of 3
Previous123 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Uploading a module that's bigger than web.config's max upload sizeUploading a module that's bigger than web.config's max upload size


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