John Mitchell
Posts:4384
Administrator
Send PM:
 | | 18 Feb 2008 05:45 PM | | To enable the Static File Handler for CSS and/or JS or images you will need to setup your application in IIS so that requests for these files are sent to the ASP.Net framework.
I have attached a couple images to this post to show how that is done. Along with the IIS Setup you will also need the following line added to your web.config in the httpHandlers section. PageBlaster adds this line to your web.config automatically if you have installed version 3.x. <add verb="*" path="*.css,*.js,*.jpg,*.gif,*.png"
type="Snapsis.HttpModules.PageBlaster.StaticFileHandler, Snapsis.HttpModules.PageBlaster"/>
| |
| | | | Tags: static files | |
|
|
|
Ari Doucette
Posts:57
Send PM:
| | 21 Feb 2008 11:27 AM | | What is the benefit of sending these to the static file handler? Is there a downside to this? | | | |
|
John Mitchell
Posts:4384
Administrator
Send PM:
| | 21 Feb 2008 11:16 PM | | Hi Ari, Excellent question. The benefit comes from PageBlaster being able to do caching, compression, and replacements on JS & CSS, and if you configure it to handle images it will also strip the ETag header and add expires headers for those files as well. Expires headers are what is needed to make the files stay in the cache on the user's browser and keeps the browser from having to make several requests just to find out the files have not been changed. You can set expires headers directly in IIS, and you can also do compression if your server is setup for it, but some people can't do that at the server level. The downside is that sending these static files to ASP.Net and letting PageBlaster handle them may be a little slower than IIS on the first request, but it really helps to optimize how they are stored at the client. Sending them to PageBlaster also allows you to configure the expire times by page where if you do it in IIS it is for the whole site. You can learn more about these optimizations here: http://developer.yahoo.com/performance/rules.html | | | |
|
Patrick Coleman
Posts:89
Send PM:
| | 28 Jun 2009 12:40 PM | | Hey John,
Does Page Blaster have an automatic setting for content expiry once the static page handler is enabled or do we still have to set it manually for every page in the site by adding an instance to the page?
If I configure the content to expire in 30 days for one page and then tell the module to display on all pages would this get the desired affect of having all pages content expire in 30 days?
Thanks,
Pat | | | Changing the world one spine at a time - Chiropractic Websites | |
|
John Mitchell
Posts:4384
Administrator
Send PM:
| | 28 Jun 2009 12:50 PM | | Content expiry for static resources is set using the disk-cache-interval. You can set it individually per page, because they are requests for resources that may come from any page. | | | |
|
Pieter Van Tichelen
Posts:13
Send PM:
| | 12 Nov 2009 03:13 AM | | Hi John,
I'm a happy customer of PageBlaster and have been using it now for several months (in combination with iFinity URLMaster on DNN5.1.4 - great combination!). As I have some time to spare, I'd like now to set up the static file handler for my dotnetnuke sites.
My shared web hosting is running on IIS7, so can you tell me if there is anything different from the instructions for IIS5/6?
Thanks in advance,
Pieter | | | |
|
Gaz
Posts:10
Send PM:
| | 13 Nov 2009 03:23 AM | | I'd like to know how to set this up on IIS7 as well. This could possibly be why pageblaster isn't working correctly for me.
G | | | |
|
TeresaS
Posts:4
Send PM:
| | 26 Jan 2010 03:07 PM | | we are on Mosso Cloud Sites environment. It is not allow to configure IIS for a wildcard mapping of ASP.Net to our website. Also our website is a secure website. The website content is controlled by role after successful login. Only login and register pages are available before login. What can we do to benefit from PageBlaster in this situation? | | | |
|
John Mitchell
Posts:4384
Administrator
Send PM:
| | 26 Jan 2010 03:14 PM | | Hi Teresa,
You can still get a huge benefit from caching unauthenticated users, and with the automatic merging of CSS & JS files. | | | |
|
TeresaS
Posts:4
Send PM:
| | 26 Jan 2010 03:46 PM | | Thanks John. We have no unauthenticated users. On the PageBlaster.config, I noticed that lines - cached-role="" and cache-users="", can we put roles and users into "", how can we use regular expression for all role and all users ? | | | |
|
TeresaS
Posts:4
Send PM:
| | 26 Jan 2010 03:48 PM | | Thanks John. We have no unauthenticated users. On the PageBlaster.config, I noticed that lines - cached-role="" and cache-users="", can we put roles and users into "", how can we use regular expression for all role and all users ? | | | |
|
John Mitchell
Posts:4384
Administrator
Send PM:
| | 26 Jan 2010 03:59 PM | | Yes, you can cache users, but the return on performance may not be worth it.
Each page is cached separately for every user, so unless that same user is viewing the same information over and over it may not help.
Partial caching of the page (module caching) is usually a better way to go if you can.
If you want to try out user caching, the expression to cache all users would be cached-users=".*" | | | |
|
TeresaS
Posts:4
Send PM:
| | 26 Jan 2010 04:06 PM | | Can you give me advice on Partial caching of the page? Thanks | | | |
|
John Mitchell
Posts:4384
Administrator
Send PM:
| | 26 Jan 2010 04:19 PM | | Sure, under Module Settings, for a module there is a cache time setting.
Set it to a number of seconds that you want to cache the module output for.
I also recommend that you set the Module Caching to Memory in Host Settings. By default it is set to Disk, which can be a lot slower than memory. | | | |
|
Pieter Van Tichelen
Posts:13
Send PM:
| | 15 Feb 2010 06:27 AM | | Hi, It's been about three months now. Did you per chance had any luck looking into this? thx Pieter
Posted By Pieter Van Tichelen on 12 Nov 2009 03:13 AM
Hi John,
I'm a happy customer of PageBlaster and have been using it now for several months (in combination with iFinity URLMaster on DNN5.1.4 - great combination!). As I have some time to spare, I'd like now to set up the static file handler for my dotnetnuke sites.
My shared web hosting is running on IIS7, so can you tell me if there is anything different from the instructions for IIS5/6?
Thanks in advance,
Pieter
| | | |
|
John Mitchell
Posts:4384
Administrator
Send PM:
| | 15 Feb 2010 08:43 AM | | For IIS7, if you are running in integrated mode, all you need to do is enable the StaticFileHandler in the web.config by removing the comments: <add name="PageBlasterHandler" verb="*" path="*.css,*.js,*.gif,*.jpg,*.jpeg,*.png" type="Snapsis.HttpModules.PageBlaster.StaticFileHandler, Snapsis.HttpModules.PageBlaster" preCondition="managedHandler" /> | | | |
|
Pieter Van Tichelen
Posts:13
Send PM:
| | 15 Feb 2010 09:17 AM | | Thanks, that's what I needed to know. Just the one question though: no extension mapping changes needed on the IIS? (As I don't know how to do this in IIS7.) | | | |
|
John Mitchell
Posts:4384
Administrator
Send PM:
| | 15 Feb 2010 09:23 AM | | No mapping is needed on IIS7 in integrated pipeline mode. The configuration in web.config does the mapping. | | | |
|