Issues with DasBlog

Hello,

We were really hoping to use the PageBlaster as a compression alternative to Blowery after we simply gave up with exclusions as we could never get it to work with WebResource.axd, Ajax, etc.

So we were pretty excited to test this out before buying, however, we are getting some very ugly results.

1. First time we go to a page, it often comes back as blank with just HTML and BODY tags. We checked the /cache folder and there is a file there
2. If we refresh, the page MAY return with our actual HTML but it will have no styles rendered at all...as if all our style sheets were completely missed (they are simply css files in another folder)

In the web.config of a dasblog application, we placed the HttpModule after the dasblog rewriting:

addname="PageBlaster"type="Snapsis.HttpModules.PageBlaster.PageBlasterModule, Snapsis.HttpModules.PageBlaster" />

Thanks John, but unfortunately, that's not the case. I checked for html, body, and head and there is only one.

For instance, I just placed the module back in to the web.config, started debugging and all I got was this for the page that loaded:

That's not the same DOCTYPE, header, or anything that any of our pages have in the site.

I checked the /cache folder and there is indeed a new file there.

I hit refresh and the page does comes back, but without the CSS styles applied.

http://www.findinternettv.com/ would be the site where we would leverage this.

Our other concern with using your software is that we have many different page parameters throughout the site depending on the page one is on.