Hi John -

We seem to be having a strange error when we installed PB. It seems that you can visit a page once and it will be fine, then if you visit or refresh the page, it cannot be found. All that was done was we installed PB, added a custom rule and later removed the rule. We are also using the Ifinity URL Master module, so I'm not sure if that has anything to do with it. The site works fine if we remove PB. Thanks!

Tried that and we still get the same problem.

This is the error in FF

Content Encoding Error
  

The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.
The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.

    * Please contact the website owners to inform them of this problem.

Maybe you still have the DNN core compression module listed in the httpModules section of web.config?

Hello Marc;

I'm having the same problem!  Refer to this thread:

http://www.snapsis.com/Support/tabid/601/forumid/9/postid/11530/view/topic/PageBlaster-w-IIS----Server.aspx

and you can see what I've tried so far.  It comes back using FiddlerV2 that it is a problem with the compression header, but it has something to do with caching as well.  When I disable caching on portal, it runs fine, just not caching.  If I disable compression and leave caching enabled, it runs as well but also ignores any rules that have been set up. Fiddler says it's sending a file over, slightly larger than the original load (although original load was in pieces so it's hard to be sure), but cannot decompress it as "invalid header".  What version of IIS are you running?  I'm running IIS7.  I'd be more than happy to share everything I've tried so far and my exact config.

I've also posted this at iFinity as well, but haven't received a reply yet.  However, I'm also pretty sure at this point it has nothing to do with their module unless it's a fluke setting.  I've tried every setting combination for these two together that anyone else has had success with!

D

Does this issue with the page not being able to be displayed only happen if you have both PageBlaster and the Url Master module running together, or does it still happen with just PageBlaster running?

I'll see if I can get a copy of Url Master and do some testing.

If someone can attach their web.config (after removing any sensitive info) that will help.

Here you go John, this is my web.config.  You can download url Master from iFinity for free.  Trial version just adds a page tag that reads "trial version, etc."  They will also give a 10 day key for free or in this case he would probably even give you a development key.  It's Monday morning there so he'll probably be responding to requests in a couple hours.

Anything I can do to help with this just let me know.  We are pretty much shutdown on web design until I resolve this as every time I try a change it shuts everyone down.

Thanks,

D

Hi John,

Is there an emailaddress I can send you my web.config to?

Regards,

Marc

Done!

I thought that a good possibility, but I hadn't tried deleting the line myself.  I was thinking that perhaps because of the core module (or IIS compression which I double checked was turned off) we were getting a "double" compression and the second header couldn't be recovered to decrypt the cached image.  I scoured DNN pages for info on the core compression module, but posts with any real meat were sparse.  It also bothered me that web.config had only one line referring to compression and that line was in system.webserver.  An entry as a module not one as a handler.  What would IIS prior to 7 do to call the compression handler?

What order did you put PB & urlMaster in in the config file?  I'll delete the compression line right now and see what I get.

D

Also try adding this line to the httpHandlers

            < remove name="StaticCompressionModule" />

I've been trying to recreate this and haven't been able to yet, but I'll keep working on it.

Well, I had moved both modules to the first items in config previously, trying url Master first and also trying PageBlaster first.  It didn't make any difference before.  Just now, I also deleted the commented out line on compression in the system.webserver section.  It didn't make any difference except that now I'm getting 500 server errors when I restart in host settings.  I refresh the page and it appears and all seem fine.  Same errors in PageBlaster settings and url Master settings too.  Just from deleting compression line?  That makes me even more believe it's a dual compression conflict issue.

Marc, do you have IIS6 or IIS7?

John, I'll add that line to my handlers section but do I need and "add name" similar for system..webserver?  I'll report back in a few.

D

John;

I tried that line in both handler and module sections without change. Since you are having a problem recreating this error, would it be easier if I just gave you my url, host login and hosting account ftp?

I've not only had no luck, since deleting the commented out compression line from the system.webserver section I've had issues with repeated 500 errors on admin and host pages.  Issues with adding and editing pages, etc.  It's got to be a compression issue.  Is yours still running?  I'm on IIS7 and my solution will be slightly different, assuming that the cause is the same, as it seems to be.

John posted he was having trouble recreating the errors and I offered to send him my logins so he could experience them on my portals, but haven't heard back from him yet.  I've tried every combination of everything we've discussed so far, and more. 

My presumption is this:  I clear cache and can surf pages as long as I start on a page and only revisit a page by the back button.  As soon as I try to access the page by clicking it in the menu (a page I have already visited since clearing cache), then I get the error.  Invalid gzip compression header.  I think what is happening is that when using the back button, I'm accessing the page from server memory, but when I navigate by selecting in the menu, it is serving the page from disk.  Once the page is cached, the cache image that is served from disk has an issue with the compression that is corrupting the header or making the browser unable to read it.  Maybe double compression from the core module.  Since disabling either cache or compression allows the site to run without error, and I get the error only when both are enabled, it's a reasonable deduction.

I'm getting desparate here.  Been fighting this for 2 weeks now and production on our sites has come to a total stop.

D