Upgrade 2399 > 2400 - web.config ?

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
12/4/2013 7:00:04 AM
Ken Evans
Gravatar
Total Posts 77
View Posts

Upgrade 2399 > 2400 - web.config <security> ?

In my "old" 2399 web.config I have commented out the following code (between lines 1087 and 1093):
  <!--
    <security>
      <requestFiltering>
        <requestLimits maxAllowedContentLength="31457280"/>
      </requestFiltering>
    </security>
    -->

However, in the new 2400 web.config, this code (between lines 1097 and 1101) is not commented out.

I don't know why the 2399 web.config has these lines commented out.

Please will someone explain:
1) The purpose of this code?

2) Whether it should be commented out or not in the 2400 version?
 

 Thanks

 Ken

12/4/2013 9:56:18 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Upgrade 2399 > 2400 - web.config ?

It was uncommented in the new one by accident. The main reason it is intended to be commented out by default is because in some environments it would cause an error if those settings are locked down at a higher level so we were just trying to avoid an error that could crash the site in some environments.

It is a very useful setting to uncomment because it affects how large of files can be uploaded, this settings is discussed in the article Supporting Large File Uploads.

So if it causes you no errors (and it should cause none in most environments) then that is good.

Best,

Joe

 

12/4/2013 10:44:27 AM
Ken Evans
Gravatar
Total Posts 77
View Posts

Re: Upgrade 2399 > 2400 - web.config ?

I have not yet tested the new web.config so I don't yet know whether it will cause any errors.
However, I have commented out the code in the 2.4.0.0 web.config.

Thanks

Ken
 

You must sign in to post in the forums. This thread is closed to new posts.