Position of the PageBlaster entry in the web.config file

Hi John

I'm a little confused... I'm updated a few sites with the last snapsis pageblaster (version 2.2.4).
In this thread
http://www.snapsis.com/Support/SnapsisnbspSupport/tabid/601/forumid/9/postid/5323/view/topic/Default.aspx
You've said...
Also, make sure that the PageBlaster entry in the HttpModules section of web.config is the first entry (before UrlRewriter).

In this thread and also in the Snapsis.PageBlaster.readme.txt you said:
http://www.snapsis.com/Support/SnapsisnbspSupport/tabid/601/forumid/9/postid/5745/view/topic/Default.aspx
that the PageBlaster entry in the HttpModules section of web.config had to be set after UrlRewriter...

What's the difference?
Why you have said this in this thread?
http://www.snapsis.com/Support/SnapsisnbspSupport/tabid/601/forumid/9/postid/5323/view/topic/Default.aspx

Hi Gilbert,
The difference is subtle, but may be needed in certain situations.

If the UrlRewriter is listed after the PageBlaster, then PageBlaster will see links as they look after they have been re-written, so the excludes may need to be written differently. 
In other words, for a link that is a Friendly URL like this :
          http://www.mysite.com/Home/tabid/36/default.aspx
PageBLaster will actually see the Link as :
         http://www.mysite.com/default.aspx?tabid=36

On the other hand, if UrlRewriter is listed before the PageBlaster , then PageBlaster will see the link as it looks in the address bar before it is Rewritten.  So in this case what you see in the address bar is also what PageBlaster uses to compare for excludes, etc.

The rule for HttpModules is that the First One in the list will be the Last One executed known as First-In-Last-Out (FILO).  For PageBlaster this is important to make it near the first of the list since it does compression on the page output.  Otherwise all the rest of the modules will only get the compressed page output to work with.  For the UrlRewriter this doesn't matter since it is only manipulating the Url, and you can move it around to fit your situation.

My main goal in the readme for the install is to get people to list it where what they see in the address bar is what they can also use for excludes.

Thanks John

Hi John

I've updated a few dnn sites to dnn 04.05.04.
And now I want to setup pageblaster again.
I've seen that there are a few lines more in the HttpModules section in web.config

[!-- HttpModules for Common Functionality --]
[httpModules]
[add name="Compression" type="DotNetNuke.HttpModules.Compression.HttpModule, DotNetNuke.HttpModules.Compression"/]
[add name="RequestFilter" type="DotNetNuke.HttpModules.Compression.RequestFilter.HttpModule, DotNetNuke.HttpModules.Compression" /]
[add name="UrlRewrite" type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules.UrlRewrite"/]
[add name="PageBlaster" type="Snapsis.HttpModules.PageBlaster.PageBlasterModule, Snapsis.HttpModules.PageBlaster" /]
[/httpModules]

In your Snapsis.PageBlaster.readme.txt file
You've said that you've to remove the following line:
[!-- [add name="Compression" type="DotNetNuke.HttpModules.Compression.HttpModule, DotNetNuke.HttpModules.Compression"/] --]
(do not use the compression from dnn)

I think that in the new dnn version 04.05.04 I've to remove also the following line:
[!-- [add name="RequestFilter" type="DotNetNuke.HttpModules.Compression.RequestFilter.HttpModule, DotNetNuke.HttpModules.Compression" /] --]

Is that correct?...
What does the requestFilter exactly?

PS
The < is changed to [
The > is changed to ]
in the above code.

Hi Gilbert,
You do not need to remove the request filter, although you may not need it.  It allows you to block, and redirect incoming requests based on parameters in the Request.ServerVariables collection.

Mitchel Sellers has a tutorial on the request filter here:

http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/118/Using-DotNetNuke-Request-Filter.aspx 

Hi John

Thanks for your respons...