Hi,
I originally posted this in the DNN forum but haven't recevied any replies. I'm hoping someone can shed some light on this for me.

After upgrading to IE8 I was no longer able to access my localhost DNN site on either IE8 or Firefox. After some trial and error I wound up disabling pageblaster in web.config and was able to access the site. Everything is working fine on our production site - www.imisoftwareinc.com. This is only an issue on my local machine. Firefox displays an error stating unrecognized compression.

Any ideas?

Thanks,
Vinny

Hi Vinny,
I tried using IE8 on a localhost site and cannot reproduce this problem.

Maybe if you completely clear out the PageBlaster cache it'll fix it. You can also try changing the location of the PageBlaster line in the httpModules section of web.config. Keep it towards the top, but move it up or down 1 or two places as it relates to the other modules.

Thanks for the quick reply! I'll try both suggestions and see what happens.

Hi,
I tried both clearing the cache and moving the line up in the httpModules section. Once I cleared the cache I was able to view my home page but when I navigate to another page, then back to the home page (or any page I previously viewed) I'm unable to view it again. Firefox tells me the problem is an unsupported form of compression.

I am currently demoing the trial version of the iFinity UrlMaster module. I disabled UrlMaster and the problem was fixed. I was using the FriendlyUrl from iFinity so I reset my web.config to use that and it worked fine.

It appears to be a conflict somewhere between PageBlaster and the iFinity UrlMaster module but only after I upgraded to IE8. I tried adding iFinity.UrlMaster to the exclude paths in the PageBlaster config file but it still didn't correct the problem.

Any other ideas would be appreciated. Thanks.

Thanks

Oh, that is a known issue with the iFinity module.
There are details about that here:
http://www.ifinity.com.au/Products/Support_Forums/forumid/8/threadid/522/scope/posts/threadpage/6

I'm not sure why it only showed up when you started using IE8

Great. Thanks for your help and the link to the thread. I'm not sure why it only showed up after the IE8 upgrade. I guess it's possible that I did more robust testing after the IE8 upgrade and so I attributed it to that. But either way I at least know what the problem is now. I requested a 10-day no message license from iFinity so I can test appropriately.

Thanks again for the quick replies!