I have quickly learned that I need to test all of my custom modules against PageBlaster to make sure nothing breaks, and to find any needed rules to allow the module to function as expected. Right now, I have PageBlaster running on a staging site to simuate our live site. However, I am having some VERY strange things happen, and I need to disable PageBlaster temporarily to see if these new issues are from PageBlaster, or somewhere else. I have commented out the PageBlaster line in the httpModules section of the web.config. Is there anywhere else where I need to make a change to disable compression AND caching for the entire site? |