FastMVC: Compress and Cache Dynamic and Static requests

NEW POST: .swf flash component not getting loaded by trying this

hrdksanghavi — Wed, 03 Jun 2009 12:00:54 GMT

Hi!
I tried this, the output is good, but only one problem i have is the Flash component are not getting loaded.
It only shows the empty block and when I right click on it, it shows "not loaded". But If I Remove both the .cs files and run the application without compression, the flash gets displayed.
So is there any more work to do this?

NEW POST: Will this work for plain asp.net webform applications??

ajitgoel — Mon, 23 Mar 2009 02:59:56 GMT

I was planning to implement something like this in my asp.net application. Will this http module work for plain asp.net webform applications??

NEW POST: Duplicating existing code

taliesins — Tue, 17 Mar 2009 10:07:35 GMT

I believe you are looking for this method:

private static string MimeType(string fileName)
{
FileInfo fileInfo = new FileInfo(fileName);
string fileExtension = fileInfo.Extension.ToLower();

string cacheKey = "MimeTypeFor" + fileExtension;
object cachedValue = HttpRuntime.Cache.Get(cacheKey);
if (cachedValue != null)
return (string)cachedValue;

string mime = "application/octetstream";
Microsoft.Win32.RegistryKey rk = Microsoft.Win32.Registry.ClassesRoot.OpenSubKey(fileInfo.Extension.ToLower());
if (rk != null && rk.GetValue("Content Type") != null)
mime = rk.GetValue("Content Type").ToString();

HttpRuntime.Cache.Add(
cacheKey,
mime,
null,
//TODO: ideally we should have a dependency on the web.config file to refresh the cache when modified
System.Web.Caching.Cache.NoAbsoluteExpiration,
new TimeSpan(0, 20, 0),
System.Web.Caching.CacheItemPriority.Normal,
null);

return mime;
}

Regards
Taliesin

NEW POST: Duplicating existing code

ndsm — Fri, 27 Feb 2009 09:26:15 GMT

It seems that all your code is duplicating existing code in IIS or in ASP.NET. I mean, you even have your own list of MIME types! It's a lot of code to accomplish a simple task.

Is there really no way to leverage existing code instead of brewing all this own?

UPDATED WIKI: Home

oazabir — Mon, 30 Jun 2008 11:01:21 GMT

Why FastMVC?

Load dynamic pages 5 to 20 times faster by compressing response on the fly
Serve static files (js, html, css) 10 to 100 times faster by compressing and caching their content
Improve repeated site load time by maximizing caching on browser

Problem

There are several problems with ASP.NET MVC application when deployed on IIS 6.0:

Extensionless URLs give 404 unless some URL Rewrite module is used or wildcard mapping is enabled
IIS 6.0 built-in compression does not work for dynamic requests. As a result, ASP.NET pages are served uncompressed resulting in poor site load speed.
Mapping wildcard extension to ASP.NET introduces the following problems:

Slow performance as all static files get handled by ASP.NET and ASP.NET reads the file from file system on every call
Expires headers doesn't work for static content as IIS does not serve them anymore. Learn about benefits of expires header from here. ASP.NET serves a fixed expires header that makes content expire in a day.
Cache-Control header does not produce max-age properly and thus caching does not work as expected. Learn about caching best practices from here.
After deploying on a domain as the root site, the homepage produces HTTP 404.

Solution

We need to write a custom static file handler that will cache small files like images, Javascripts, CSS, HTML and so on in ASP.NET cache and serve the files directly from cache instead of hitting the disk. Here are the steps:

Install an HttpModule that installs a Compression Stream on Response.Filter so that anything written on Response gets compressed. This serves dynamic requests.
Replace ASP.NET's DefaultHttpHandler that listens on . for static files.
Write our own Http Handler that will deliver compressed response for static resources like Javascript, CSS, and HTML.

Download the latest code from "Downloads" tab

Read on

Read details about this on my blog:

http://msmvps.com/blogs/omar

UPDATED WIKI: Home

oazabir — Mon, 30 Jun 2008 11:00:01 GMT

Why FastMVC?

Load dynamic pages 5 to 20 times faster by compressing response on the fly
Serve static files (js, html, css) 10 to 100 times faster by compressing and caching their content
Improve repeated site load time by maximizing caching on browser

Problem

There are several problems with ASP.NET MVC application when deployed on IIS 6.0:

Extensionless URLs give 404 unless some URL Rewrite module is used or wildcard mapping is enabled
IIS 6.0 built-in compression does not work for dynamic requests. As a result, ASP.NET pages are served uncompressed resulting in poor site load speed.
Mapping wildcard extension to ASP.NET introduces the following problems:

Slow performance as all static files get handled by ASP.NET and ASP.NET reads the file from file system on every call
Expires headers doesn't work for static content as IIS does not serve them anymore. Learn about benefits of expires header from here. ASP.NET serves a fixed expires header that makes content expire in a day.
Cache-Control header does not produce max-age properly and thus caching does not work as expected. Learn about caching best practices from here.
After deploying on a domain as the root site, the homepage produces HTTP 404.

Solution

Install an HttpModule that installs a Compression Stream on Response.Filter so that anything written on Response gets compressed. This serves dynamic requests.
Replace ASP.NET's DefaultHttpHandler that listens on . for static files.
Write our own Http Handler that will deliver compressed response for static resources like Javascript, CSS, and HTML.

Read on

Read details about this on my blog:

http://msmvps.com/blogs/omar

UPDATED WIKI: Home

oazabir — Mon, 30 Jun 2008 10:59:18 GMT

Why FastMVC? !

Load dynamic pages 5 to 20 times faster by compressing response on the fly
Serve static files (js, html, css) 10 to 100 times faster by compressing and caching their content
Improve repeated site load time by maximizing caching on browser

Problem !

There are several problems with ASP.NET MVC application when deployed on IIS 6.0:

Extensionless URLs give 404 unless some URL Rewrite module is used or wildcard mapping is enabled
IIS 6.0 built-in compression does not work for dynamic requests. As a result, ASP.NET pages are served uncompressed resulting in poor site load speed.
Mapping wildcard extension to ASP.NET introduces the following problems:

Slow performance as all static files get handled by ASP.NET and ASP.NET reads the file from file system on every call
Expires headers doesn't work for static content as IIS does not serve them anymore. Learn about benefits of expires header from here. ASP.NET serves a fixed expires header that makes content expire in a day.
Cache-Control header does not produce max-age properly and thus caching does not work as expected. Learn about caching best practices from here.
After deploying on a domain as the root site, the homepage produces HTTP 404.

Solution !

Install an HttpModule that installs a Compression Stream on Response.Filter so that anything written on Response gets compressed. This serves dynamic requests.
Replace ASP.NET's DefaultHttpHandler that listens on . for static files.
Write our own Http Handler that will deliver compressed response for static resources like Javascript, CSS, and HTML.

Read on !

Read details about this on my blog:

http://msmvps.com/blogs/omar

UPDATED WIKI: Home

oazabir — Mon, 30 Jun 2008 10:58:41 GMT

!Why FastMVC?!
Load dynamic pages 5 to 20 times faster by compressing response on the fly
Serve static files (js, html, css) 10 to 100 times faster by compressing and caching their content
Improve repeated site load time by maximizing caching on browser

!Problem!
There are several problems with ASP.NET MVC application when deployed on IIS 6.0:

Extensionless URLs give 404 unless some URL Rewrite module is used or wildcard mapping is enabled
IIS 6.0 built-in compression does not work for dynamic requests. As a result, ASP.NET pages are served uncompressed resulting in poor site load speed.
Mapping wildcard extension to ASP.NET introduces the following problems:

Slow performance as all static files get handled by ASP.NET and ASP.NET reads the file from file system on every call
Expires headers doesn't work for static content as IIS does not serve them anymore. Learn about benefits of expires header from here. ASP.NET serves a fixed expires header that makes content expire in a day.
Cache-Control header does not produce max-age properly and thus caching does not work as expected. Learn about caching best practices from here.
After deploying on a domain as the root site, the homepage produces HTTP 404.

!Solution!
We need to write a custom static file handler that will cache small files like images, Javascripts, CSS, HTML and so on in ASP.NET cache and serve the files directly from cache instead of hitting the disk. Here are the steps:

Install an HttpModule that installs a Compression Stream on Response.Filter so that anything written on Response gets compressed. This serves dynamic requests.
Replace ASP.NET's DefaultHttpHandler that listens on . for static files.
Write our own Http Handler that will deliver compressed response for static resources like Javascript, CSS, and HTML.

!Read on!
Read details about this on my blog:

http://msmvps.com/blogs/omar

CREATED RELEASE: Version 1.0 (Jun 30, 2008)

Mon, 30 Jun 2008 10:55:40 GMT

UPDATED WIKI: Home

oazabir — Mon, 30 Jun 2008 10:53:30 GMT

Problem
There are several problems with ASP.NET MVC application when deployed on IIS 6.0:

Extensionless URLs give 404 unless some URL Rewrite module is used or wildcard mapping is enabled
IIS 6.0 built-in compression does not work for dynamic requests. As a result, ASP.NET pages are served uncompressed resulting in poor site load speed.
Mapping wildcard extension to ASP.NET introduces the following problems:

Slow performance as all static files get handled by ASP.NET and ASP.NET reads the file from file system on every call
Expires headers doesn't work for static content as IIS does not serve them anymore. Learn about benefits of expires header from here. ASP.NET serves a fixed expires header that makes content expire in a day.
Cache-Control header does not produce max-age properly and thus caching does not work as expected. Learn about caching best practices from here.
After deploying on a domain as the root site, the homepage produces HTTP 404.

Solution
We need to write a custom static file handler that will cache small files like images, Javascripts, CSS, HTML and so on in ASP.NET cache and serve the files directly from cache instead of hitting the disk. Here are the steps:

Install an HttpModule that installs a Compression Stream on Response.Filter so that anything written on Response gets compressed. This serves dynamic requests.
Replace ASP.NET's DefaultHttpHandler that listens on . for static files.
Write our own Http Handler that will deliver compressed response for static resources like Javascript, CSS, and HTML.

Read on
Read details about this on my blog:

http://msmvps.com/blogs/omar