Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 03/31/2008 4:56 PM by  petersk
DNN 04.04.01 and compression
 7 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
01/26/2007 5:54 PM

    Hi All,

    Note that DNN 04.04.01 has by default http compression turned on. This is great for performance but it does wreck any file transfers. So you need to make sure these are excluded from the compression. You do this by:

    1. Opening Compression.config in the DNN root

    2. Adding 'DesktopModules/Bring2mind/DMX/Download.aspx' to the list of excludedPaths

    3. Reset IIS for safety's sake (I'm not sure if these paths are cached somewhere)

    Report back here if you have any issues regarding file up/download and don't forget to mention what file type is involved.

    Peter Donker

    Bring2mind

    optospeed
    New Member
    New Member
    Posts:15


    --
    02/06/2007 12:09 AM

    This doesn't work for me. I disabled the host-wide compression and also added the indicated line in the compression.config file. Unfortunately, nothing changed.... Every download gets stuck a few kilobytes from the end, and as a result the file is corrupted. The uploaded file, on the server filesystem, is OK.

    Running DNN 4.4.0. & DMX 03.04.06

    Downloading 2Mbyte PDF files

    Please help.

    Andrea

    optospeed
    New Member
    New Member
    Posts:15


    --
    02/06/2007 12:54 PM
    FIXED! For some reason, the configuration settings (both in the host control panel and in the compression.config file) are not effective, at least on my installation.
    To make everything work I had to remove from the web.config file the following line:



    Now DMX is working fine.
    Andrea
    optospeed
    New Member
    New Member
    Posts:15


    --
    02/06/2007 12:56 PM

    Opss... Seems that the web.config line has been stripped out. Retrying....

    FIXED! For some reason, the configuration settings (both in the host control panel and in the compression.config file) are not effective, at least on my installation.
    To make everything work I had to remove from the web.config file the following line:

    add name="Compression" type="DotNetNuke.HttpModules.Compression.HttpModule, DotNetNuke.HttpModules.Compression"

    Now DMX is working fine.
    Andrea

    Peter Donker
    Veteran Member
    Veteran Member
    Posts:4536


    --
    08/24/2007 11:47 AM
    OK, great. Note that 04.x.00 versions are not the best option for production. With revisions new bugs are invariably introduced to a complex product like DNN. They are usually quite quick to fix these and release bugfix updates.
    petersk
    New Member
    New Member
    Posts:2


    --
    03/18/2008 11:24 PM
    would you please post the exact syntax for the new .config file? I put the path between the tags, but I have a feeling there's something a little more complex to it somehow... quotes, perhaps? does it need to be a complete path, beginning with //localhost/ or anything?

    just checking.
    Peter Donker
    Veteran Member
    Veteran Member
    Posts:4536


    --
    03/19/2008 8:57 PM

    Hi Katy,

    What Andrea posted was to remove that specific element from the web.config.

    <add name="Compression" type="DotNetNuke.HttpModules.Compression.CompressionModule, DotNetNuke.HttpModules" />

    I cannot post the whole web.config here as it might confuse others and it can be different for each DNN version and installation.

    Peter

     

     

     

    <

    petersk
    New Member
    New Member
    Posts:2


    --
    03/31/2008 4:56 PM
    I actually meant the compression.config file and not the web.config file. My apologies. So far, I've tried adding the exception path via the host settings, adding it to the compression.config, and also removing older compression .dll files (ICSharpZip) all to no avail. I'm going to try this web.config modification, but having already disabled older compression alternatives, I'm a bit wary of disabling the new built-in compression. If anyone has developed other solutions, I am still looking for a more thorough answer.
    You are not authorized to post a reply.