Version 3.0 Beta Test FeedBack

John you have missunderstood.  I have no exclusions all in the glogal config file.  On the PB screen I have Eexclude path pattern = ".*" and Exclude From = NONE

/Dave

I just found a serious problem that I assume is from PageBlaster. When I go to edit with FCKeditor I get a dialog box complaingign that it can't open .....FCKStyles.aspx.  I can request more info and get a long list.  Editing appears to work ok, but this is dis-quieting to say the least.

This appears on all pages, even one that is excluded from ".* ALL". 

This fails on all pages on both my localhost (with PB enabled in web.config) and production system.  Also the upgrade has place

3 PageBlaster lines in my web.config!

Screen captures are below.

/DaveS

Originally I wanted to exclude everything (.*) from ALL. Then when I was done testing or working on the page I would change the ALL to NONE and ingore the .*

I have removed the .*'s on all my pages.

/Dave

< excludePaths >
            < path pattern="\?(?!tabid)" excludeFrom="All" / >
          < path pattern="(\.asmx|ScriptResource\.axd|\.asxh|rss|fck|admin|install|thumb|wizard|cart)" excludeFrom="All" / >
          < path pattern="ctl.*?(edit|module|tab)" excludeFrom="All" / >
        < /excludePaths >

From PB.config  Spaces add near <  > 's  Are these excludes case insensitive?

I am runn DNN 4.8.0  and you are ?

/DaveS

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!

It does cause confusions. I have a comment line under the PB line and just move the < !-- up one line when I want to comment it out.

I never noticed the three lines until hafer I noticed that PB was still doing replacements for me.

      < add name="RequestFilter" type="DotNetNuke.HttpModules.RequestFilter.RequestFilterModule, DotNetNuke.HttpModules" / >
      < add name="UrlRewrite" type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules" / >
      < add name="PageBlaster" type="Snapsis.HttpModules.PageBlaster.PageBlasterModule, Snapsis.HttpModules.PageBlaster" / >
      < !-- Comment out the line above to disable PageBlaster - - - DWS added 9/8/07 -- >

I have similar comments by each line that I add or change in web.config. Make merging when updating real easy.

/Dave

The extension of the URL is an aspx file.

I changed nothing on the IIS. That's the postback.

 ++++++++++++++ POST

POST /Inici/tabid/60/Default.aspx HTTP/1.1
Host: dnn470
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; es-ES; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: es-es,es;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Content-Type: application/x-www-form-urlencoded
Referer: http://dnn470/Inici/tabid/60/Default.aspx

 ++++++++++++++ RESPONSE

HTTP/1.1 200 OK                                
Cache-Control: no-cache                        
Pragma: no-cache                               
Content-Length: 37772                          
Content-Type: text/html; charset=UTF-8         
Expires: -1                                    
Server: Microsoft-IIS/7.0                      
X-AspNet-Version: 2.0.50727                    
X-Snapsis-PageBlaster: v:3.0.4;c:-PNC;x:-;r:-  
Set-Cookie: language=en-US; path=/; HttpOnly   
X-Powered-By: ASP.NET                          
Date: Thu, 14 Feb 2008 22:18:47 GMT            

> 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.

Hi Dani,

Please try this scenario again with the attached DLL in your /bin folder.

Dave,

No, the exclude patterns are not case sensitive.  I am using version 4.8 also, but it's been modified.

I'll try it on a fresh install of 4.8.

Hi John,

I tried the DLL (by the way, thank you very much for your hiperfast response) and the module is still failing.

Those were the responses with and without PB (note that the X-Snapsis-PageBlaster header is missing now)

POST /Inici/tabid/60/Default.aspx HTTP/1.1

Response With PB and everything excluded

HTTP/1.1 200 OK                                           
Cache-Control: no-cache                                   
Pragma: no-cache                                          
Content-Length: 43467                                     
Content-Type: text/html; charset=utf-8                    
Expires: -1                                               
Server: Microsoft-IIS/7.0                                 
X-AspNet-Version: 2.0.50727                               
Set-Cookie: language=en-US; path=/; HttpOnly              
X-Powered-By: ASP.NET                                     
Date: Thu, 14 Feb 2008 22:51:35 GMT                       
                                                          
         .....

Response Without PB (removed from web.config)

HTTP/1.1 200 OK                            
Cache-Control: no-cache                    
Pragma: no-cache                           
Content-Length: 43467                      
Content-Type: text/javascript; charset=utf-8
Expires: -1                                
Server: Microsoft-IIS/7.0                  
X-AspNet-Version: 2.0.50727                
Set-Cookie: language=en-US; path=/; HttpOnly
X-Powered-By: ASP.NET                      
Date: Thu, 14 Feb 2008 22:50:24 GMT        
                                           
     .....

thanks again John for this amazing support,

dani

Ok, here's another try attached.

And thank you for helping me test and debug.  I really appreciate it.

[Edit: I removed this DLL attachment since it didn't work.]

I have found a fairly critical bug.  I have two pages with UDT modules loaded with PDF files pointed to by DNN's crazy click-link crap.

With PB disabled in web.config the are very readable files. With it enabled they are garbage even whenexcluded ".* ALL"

The pages are Links and Docs  whic has a PB module asd is excluded, and Web Listing Docs  which has no PB module on the page.

Bring up a PDF and see how well you can read it.

/DaveS

Hello John,

Tried with the second fixed DLL (3.0.5) but no luck.   The module still fails

This is the response with PB plugged in and everything excluded

HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 37772
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.0
X-AspNet-Version: 2.0.50727
Set-Cookie: language=en-US; path=/; HttpOnly
X-Powered-By: ASP.NET
Date: Fri, 15 Feb 2008 07:40:34 GMT

sorry for the delay, it was sleeping time in spain. Now I have a new and fresh day to help you to track it down

Ok, let's hope the third time is a charm.  I have attached a new DLL to try.

Dave,

I was able to recreate both problems you were having with the PDF download and with the Styles in the FCK editor.  The reason I wasn't seeing the error is because the styles thing only happens if you have set the editor to use custom/dynamic styles.  The attached DLL should fix those issues also.

All of the issues were related to setting the Content-Type of the response.

yes! it works!

now the affected module works with and without Pageblaster! GREAT!

definitely this is the dotnetnuke killer app!

thank you very much!

dani

It seems to fix both of my issues --- Thanks

/DaveS