PB is commented out, but site is still compressed?

Rate this topic:

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

Author

Messages

Ari Doucette
<100 Posts

Posts:58

11/13/2007 7:07 AM
Hi, I currently have PageBlaster (Free and Paid) and the PageBlaster line is commented out in the web.config. If I visit pipeboost.com, and run the compression analyzer tool, it shows that my site is compressed with gzip. I know that the core DNN compression is also commented out in the web.config. So what's going on? Where is the compression coming from? I'll paste the config lines below.

John Mitchell
Posts:3248

11/13/2007 9:33 AM
It may be that you have compression enabled in IIS.

Ari Doucette
<100 Posts

Posts:58

11/13/2007 10:31 AM
Thank you, John. Right as usual! So, I guess my next question should be: what are the advantages and disadvantages of using IIS6 http compression with a DotNetNuke site if PageBlaster is turned on? Does it just act to compress if PB compression is turned off?

John Mitchell
Posts:3248

11/13/2007 10:39 AM
If compression is enabled in IIS then you should disable it in your web applications. You don't want to compress pages more than once, even if it happens to work it is a waste of processing. IIS compression performance is a little better since it can do it at a lower level, but it is not as flexible if you run into problems. IIS doesn't know if the application is doing it's own compression. If you want to run PageBlaster and let IIS do the compression then you can do so by putting an exclude pattern into the Snapsis.PageBlaster.config file: pattern=".*" excludeFrom="Compression"

Ari Doucette
<100 Posts

Posts:58

11/13/2007 10:48 AM
So it is better to use either IIS compression or PB compression (but not both). And IIS compression is better to use than PB compression? You mention "IIS compression performance is a little better since it can do it at a lower level, but it is not as flexible if you run into problems." There are lines in the PB config that are set to excludeFrom="All". So are these things that IIS compression might "choke" on? But if I always had IIS compression running (w/o knowing it) and PB, then IIS was always compressing these things w/o problems, right? (these are all questions, if some of them read like statements, or as rhetorical, I still intend them as questions b/c I don't know the answers...) So, it sounds like the thing to do is put "pattern=".*" excludeFrom="Compression"" into PB's config, and let IIS handle the compression from now on. So, for the rest of the items in PB config, that read excludeFrom="All", do I need to change the "All" or just leave it as it is?

John Mitchell
Posts:3248

11/13/2007 10:59 AM
I wouldn't say IIS compression is "better" than PB compression, but that is a subjective statement either way. If you are running IIS compression and don't need the flexability that PageBlaster gives you then IIS compression will perform a little better. Yes, the lines in the PB config file that have excludefrom="ALL" are things that IIS "might" choke on, but IIS can be configured to avoid those things too, it's just not as straight forward and is done on a machine level instead of at the individual websites. If you were always running IIS compression and didn't notice any problems then it should be safe to continue with that. Don't change anything in PageBlaster that says excludeFrom="All" because those things still need to be excluded from having any type of response filter applied.

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

Forums >Snapsis Product Support >PageBlaster > PB is commented out, but site is still compressed?