DavidWSnow
 Posts:177

| | 02/19/2008 7:32 PM |
| I vote early and often for the cache flush - DaveS I have just discovered a new problem. I have to UDT modules that Have PDF files in them. Located on Links and Docs and Web Service Docs. When every I click on the crazy DNN link-click url the system hangs waiting for the server. With page exclusions rules of ".* ALL" it still fails. If I edit the web.conf and stop PB it works. I suspect that the exclusion really needs to be on LinkClick.aspx and nor on the page that I have them. Help, /Dave | | | |
|
John Mitchell Posts:3085


| | 02/19/2008 9:48 PM |
| Hi Dave, Excluding LinkClick is a good idea. You can add it to the list in this one: path pattern="(LinkClick|\.asmx|ScriptResource\.axd|\.ashx|rss|fck|admin|install|thumb|wizard|cart)" excludeFrom="All" | | | |
|
DavidWSnow
 Posts:177

| | 02/20/2008 5:08 PM |
| I have added LinkClick to the exclusions rules and all works well. Can I assume that you will be adding this to your default config file? /Dave | | | |
|
John Mitchell Posts:3085


| | 02/20/2008 5:32 PM |
| Yes, I think it would be a good idea to have that exclusion in the default config file.
How's the YSlow score coming along? | | | |
|
DavidWSnow
 Posts:177

| | 02/20/2008 6:02 PM |
| On a page with just and HTML module and no "addthis" link in the skin I get a C 70. On my home page with 3 module a container with "addthis" and a few images I get D 60 and have actually gone down by 3. After getting caught by the LinkClick got-ya I am testing the site a bit more. Active module would fall off the right ride of the screen when viewing a post in IE. I had though that this was a bug in AF with div based skins and containers. I messed around and it works ok in an old div based container of mine. I have matched beginning and ending divs and they are matched in both containers. I haven't figured out the difference yet.
On your side I have seen some similar overlap with IE. /DaveS | | | |
|
DavidWSnow
 Posts:177

| | 02/22/2008 9:28 AM |
| John as we periodically hear of different "trace levels" for PB, I sugesst that you add a comment to the config file that lists them. It is clear that with all of the magic your have added tp V3 that there is a greater likelyhood that people will need to trace more often. Knowing the choices will help. /Dave | | | |
|
DavidWSnow
 Posts:177

| | 02/22/2008 10:14 AM |
| Since none of us can test how upgrading PB from V2.0 to V3.0 works anymore, that area may need some additional testing. During the upgrade from 3.0.4+ to V3.0.8 (on my clone), I made a copy of the PB.config file so that I could re-edit my additional rules in with yours. Your upgrade saw that I was running PB and didn't replace PB.config. Leaving my rules intact - but not giving me any changes you had made. Next I commented PB out of web.config, deleted PB.config and reinstalled. I now had a copy of the new and old PB.config and 4 copies of PB's "add verb" line in web.config. Needless to say I have no problem dealing with these minor issues, I think existing PB2.0 customers may have strange things happening, if they end up with parts of V2.0 and V3.0. I like your new I'll manage the old manual parts of the installation. I wonder if there aren't going to be some upgrade headaches for you. /Dave | | | |
|
green flash
 Posts:45

| | 02/22/2008 10:21 AM |
| | add verb duplication happened to my web.config as well :) | | DotNetNuke Türkçe | |
|
John Mitchell Posts:3085


| | 02/22/2008 10:42 AM |
| Thanks for the heads up about the duplication of the httpHandlers line for the StaticfFileHandler.
I forgot to mention that I did track that issue down last time and it is only something that is happening during beta testing because of the way I am building it as a new install each time.
People upgrading directly from 2.x to the latest build won't have this duplicated, and new installs will do the whole thing. I'll be letting people know about the auto web.config changes in the install docs and in the install post here in the forums. | | | |
|
lodani dani
 Posts:45

| | 02/22/2008 1:42 PM |
| Hello John,
I found this error in the log (using 3.0.8)
2/22/2008 5:25:30 PM PB:RequestFilter.MergeCSS: Error creating static AXD File J:\wwwroot\DnnHosted19\DesktopModules\Snapsis\PageBlaster\Cache\36d4b6edb5cc47d3ae92949960b87b4c.axd
Unable to connect to the remote server
at System.Net.HttpWebRequest.GetResponse()
at Snapsis.HttpModules.PageBlaster.StaticFileHandler.GetStaticAXD(HttpContext context, CachedRequest& cachedRequest) This error is logged for every request to a page containing a WebResource.axd call if it's not exclude in the config file. And I've got a 404 too. Once WebResource.axd it's excluded everithing works fine and the error in the log vanishes. That is extrange. How is WebResource.axd related to MergeCSS ?
thanks,
dani | | | |
|
John Mitchell Posts:3085


| | 02/22/2008 2:42 PM |
| Hi dani, It looks like you found a bug in the Error logging. Copy & Paste can do that . That error is actually in the method that gets the a static version of the virtual WebResource.axd file. It does it by making a new WebRequest back to itself. If it fails to get the file then it will return a 404. If you don't have WebPermission in your hosting environment then you will need to exclude WebResource.axd from PageBlaster like you already found out. I have attached an image that shows where you can look in the host settings page to see if you have WebPermission in your hosting environment. |

| | |
|
lodani dani
 Posts:45

| | 02/22/2008 2:55 PM |
| Hi John, I checked it and the site has WebPermission. It's running under the network service account and is a II6 on a Windows 2003. any other idea? thanks! dani | | | |
|
John Mitchell Posts:3085


| | 02/22/2008 3:07 PM |
| Ok, that can be good news if we can figure out why the error is really happening and fix it then. I have attached a debug version. If you could place both files in your /bin folder and capture the error again it may tell us more. |
Attachment: 122273579671.zip
| | |
|
lodani dani
 Posts:45

| | 02/22/2008 3:35 PM |
| thank you for your help John, here it is the full log captured with the debug version. I loaded the page two times and I've got two errors. [attachement removed after download] | | | |
|
John Mitchell Posts:3085


| | 02/22/2008 3:53 PM |
| There must be something else on the server that is blocking the request on port 80 back to itself. Or maybe DNS isn't setup on the server to resolve correctly back to your website. | | | |
|
lodani dani
 Posts:45

| | 02/22/2008 5:30 PM |
| john you were absolutely right!! The server had the firewall missconfigured and it was blocking the http requests made to itself. Currently Pageblaster is handling and compressing Webresource.axd properly. I'd like to thank you your close support in this issue and apologize for blaming PageBlaster for that problem, dani | | | |
|
DavidWSnow
 Posts:177

| | 02/22/2008 9:13 PM |
| When I checked your latest kit on my localhost clone it worked ok, but I didn't want to install it online during the day. I just installed it and started YSlowing a couple of pages to see if you had made any new improvements. PageBlaster is on and working but the YSlow score on my home page when from D-63 to F-54. Wow. Any know reason? Anything that you want me to do. What is really interesting. I recloned at 9AM this moring. On the clone's home page I get D-60 and on the online one F-54. The have the same PB config file, I ftp'ed it up after ending in my addtional rules. /DaveS | | | |
|
John Mitchell Posts:3085


| | 02/23/2008 6:02 AM |
| dani, I'm glad we got that one figured out and that you were able to take advantage of that optimization. No worries on where the problem ended up being, it could have easily been something PageBlaster needed to do different, plus we found that minor copy & paste bug.
Dave, I think it is pretty easy to jump between 54 & 60 on YSlow. My best advice would be to check each item on the performance tab to do a compare from local to live. It may be only one small difference. If you can set Content-Expiration in IIS and/or map images to ASP.Net you will see a major improvement in your score.
Ismet, Let's discuss your question in a different thread since it is not really related to the new features in PageBlaster 3.0 I'll move that and reply there. | | | |
|
allane
 Posts:9

| | 02/24/2008 5:18 AM |
| Maybe this is a bug - or maybe I've missed something: Just placed PageBlaster on the forum page of my dev-site (Active Forums) and configured a virtual directory in PB. Now all requests to /Forum/default.aspx are handled correctly. There's a problem, though. All special characters fx. the danish letters "æ ø å" are showed incorrectly. Example: ø = ø
æ = æ å = Ã¥ This only occours when requesting the page through the "Friendly-URL" handled by PB - not when requesting the "original" URL (/forum/tabid/xxx/xxx). Guess there's an encoding issue somewhere? -AllanE | | | |
|
John Mitchell Posts:3085


| | 02/24/2008 6:54 AM |
| Hi Allan, Can you describe the "when requesting the page through the Friendly-URL handled by PB" a little more? I'm not sure what that means. Is it when you assign a virtual path by putting the module on a page? Did the characters you typed above all come out as expected? I'm setting the charset to UTF-8 which always worked in the past, but that was before I had the new feature to create a static document like default.htm so maybe that is where the problem is. | | | |
|