quest4denali
Posts:63
| | 04/11/2007 9:49 AM |
| Hello,
I've found something interesting that I think is related to my skin and wondered how best to handle this through an exclusion rule.
Skin Issue: When I go to the root of my site it seems to return some badly formed html for the cache ( only in IE ). After pressing Ctrl + F5 it seems to fix the issue until the next time. This only seems to happen on my root page, for example www.bahrenburgs.com and www.bahrenburgs.com/default.aspx have the issue where www.bahrenburgs.com/Home.aspx doesn't.
If I add the entry
< path excludefrom="caching" pattern="Default\.aspx">
will that exclude only the root page, www.bahrenburgs.com and still cache the remaining pages ( unless excluded )?
| | | |
|
|
|
John Mitchell
Posts:3249
| | 04/11/2007 11:52 AM |
| Excluding default.aspx may make it exclude everything, depending on where the Url rewriter is placed in the HttpModules section in relation to the PageBlaster module.
Your home page is the most import one to cache, since that is where visitors will most likely go to first.
When you get this problem next, please do a File > "Save as" from the browser menu and send the page to me. Maybe I can see what the culprit is without having to disable it. | | | |
|
quest4denali
Posts:63
| | 04/11/2007 12:57 PM |
| Thanks John, I'll do alittle more testing and see if I can re-create it.
Just a quick follow-up, I'm not sure if this is even possible due to how pages are rendered, but is it possible to exclude just a module from compression? Just doing alittle research on the repository.
| | | |
|
John Mitchell
Posts:3249
| | 04/11/2007 1:39 PM |
| If the repository made a call back to the LinkClick page for downloads then you could just exclude that like the MakeThumbnail.aspx page for the images.
Since it does not the whole page has to be excluded. That is a POST request when you click on the download link though, so it should be excluded automatically. | | | |
|
quest4denali
Posts:63
| | 04/11/2007 3:25 PM |
| | Thanks for your help, that makes perfect sense. It also is the reason the download count and rating is not updated directly after it is made. | | | |
|
quest4denali
Posts:63
| | 04/12/2007 10:10 AM |
| Hi John,
It took me awhile to reproduce the odd display issue.
I think it might be an issue with my skin, but not 100% sure. I've attached screen shot and the html.
This only happens in IE ( 6 & 7 ). The value seems to cache until Ctrl + F5.
I'm not 100% sure if it is my skin, the PB cache, or how IE is handling HTML. I've loaded the page from the html file iteself and it seem to be jumbled as well.
| | | |
|
John Mitchell
Posts:3249
| | 04/12/2007 10:27 AM |
| Strange, when I save the text in that zip file as an html file I get the full page after opening it in IE, and I can see that it appears to be a full page by looking at the source.
I'm thinking it might be a javascript error that keeps the browser from displaying everything.
I'm pretty sure it is not PageBlaster since it appears to be a full page, unless PageBlaster is messing up a different call to get javascript, which can only happen if the javascript is embedded in asp.net (.axd file instead of .js file).
If you can do the File > Save As, and save all the contents (images, js, etc.) to a folder we may be able to tell more. | | | |
|
quest4denali
Posts:63
| | 04/12/2007 4:15 PM |
| I have a feeling it is related to the skin, but not 100% sure since it seems to work one moment and not another. I'm running a few tests on another site that has a different skin to see if there is a similar result.
I've updated the above link with all of the files (js, etc). What is interesting is it only seems to be on the default.aspx page ( www.bahrenburgs.com ). It doesn't seem to be present in any of the other pages. | | | |
|
quest4denali
Posts:63
| | 04/12/2007 10:01 PM |
| During some testing, I found that if I exclude the default.aspx from caching it doesn't cause the issue.
I've placed the UrlRewrite above PB. Any idea why the cache might be causing issues with the skin menu? It only seems to be an issue with IE. | | | |
|