replacement rule clarification

The module OptIn from Onyactech crashes when PB3.0.4 Beta is installed even if I exclude everithing in the pageblaster.config and even if I add page exclusions where the module lives on. The failure is on the Ajax request when saving the options. The postback is executed on the server but the client waits a response forever.

The only way to make the OptIn module work again is to remove the "httpModule" from the web.config

I verified that the exclusions being applied by looking at the headers of the response. I also activated the "trace level="Debug"..." to check it.

Using HttpAnalyzer I captured the response after the ajax postback produced by the optinmodule with and without Pageblaster installed and compared both with Windiff,  and the only difference appears to be in the content-type:

Postback result with pageblaster but everything excluded
Content-Type: text/html; charset=UTF-8
X-Snapsis-PageBlaster: v:3.0.4;c:-PNC;x:-;r:-

Postback result without pageblaster (removed from web.config)
Content-Type: text/javascript; charset=utf-8

is pageblaster doing something even if it is disabled?

any clue on how to debug it more in deep?

thanks!

Thanks for the detailed debug info Dani. The only time I can think of that PageBlaster would still be involved is if you have set IIS to send the extension to the StaticFileHandler and that extension is setup for the StaticFileHandler.

That Content-Type being wrong is most likely because of this scenario, because PageBlaster does attempt to set the Content-Type in the response when the StaticFileHandler is being used.

What was the extension on the url for that request?

I'll look into how this may be getting set wrong right away.

First, I'm afraid I missplaced the post. It should be at the PageBlaster beta thread.

I'm going to repost it there.

Sorry,