Dear John (and Mariette)

Today I want to try to set up the pageblaster.
I've read all your post... And you've done very good work.
In the different thread (John, Mariette, others...) you've said that many pages has to be exclude (and this for different reasons).
Has I read this threads very good I've maked for myself the following list. (for version 1, as a summary)...

<excludePaths>
   <path pattern="\?(?!tabid)"/>
  <path pattern="WebResource\.axd"/>
  <path pattern="MakeThumbImage\.aspx"/>
  <path pattern="Download\.aspx"/>
  <path pattern="Install"/>
  <path pattern="MailConnector"/>
  <path pattern="Admin"/>
  <path pattern="ftb.*aspx"/>
  <path pattern="rss"/>
>

I see now that you've make a second release. Pageblaster 1.2.

In this release you've set only one exclude path...
   

<excludePaths>
   <path pattern="\?(?!tabid)"excludeFrom="All"/>
<excludePaths>

In the last post of Mariette she said:
All newsfeeds on my site stopped working after installing PageBlaster. Trick is to add an exception for 'rss' in config file.
Your answer: Good catch Mariette and thanks for taking the time to let us know. That is because that one still has TabId as a parameter in DotNetNuke.
I guess I need to include some possible paths to exclude in the config comments.

Before I try it...
With your settings

<PATHpattern="\?(?!tabid)"excludeFrom="All"/>

By the way,

To get the XML values to show up in the post, you can wrap them with tags like this:

< code > Put code in here&nbsp;</ code >

John, Thanks for a so quick reply.
Does this mean that the following settings the only one that has to be set for a normal installation.

<excludePaths><pathpattern="\?(?!tabid)"/><pathpattern="rss"/></excludePaths>

Yes, for DotNetNuke, this is a good default.  But if you run into anything else that isn't working and it has "tabid" in it's path then you may need to exclude that also.

Please let us know if you find any other paths that need to be excluded.

Hi Gilbert,

Can you send me a link to your site?

You can also try to see if PageBlaster is properly installed yourself by going to http://web-sniffer.net/ and entering the Url to your site.

Once you get the response, look at the Response Headers section and see if it has a X-Snapsis.PageBlaster header value like the one below:

HTTP Response Header

Content (encoded: 4.90 KiB / decoded: 16.55 KiB)

Dear John

Look at this url: http://www.dnnusers.net

You are right, PageBlaster is not running on that site.

Did you add it in the httpModules section of web.config with this line of code?
It should be the forst one in that section so it'll look something like this:

<httpModules>
<addname="PageBlaster"
      type="Snapsis.HttpModules.PageBlaster.PageBlasterModule, Snapsis.HttpModules.PageBlaster"/>
<addname="UrlRewrite"
      type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules.UrlRewrite"/>
<addname="Exception"
      type="DotNetNuke.HttpModules.ExceptionModule, DotNetNuke.HttpModules.Exception"/>
<addname="UsersOnline"
      type="DotNetNuke.HttpModules.UsersOnlineModule, DotNetNuke.HttpModules.UsersOnline"/>
<addname="DNNMembership"
      type="DotNetNuke.HttpModules.DNNMembershipModule, DotNetNuke.HttpModules.DNNMembership"/>
<addname="Personalization"
      type="DotNetNuke.HttpModules.PersonalizationModule, DotNetNuke.HttpModules.Personalization"/>
>