Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

Atit — Sat, 29 Aug 2009 15:21:38 GMT

Omar, you can remove wildcard mapping on your static files and all such request will be handled by native IIS code..

blog.codeville.net/.../overriding-iis6-wildcard-maps-on-individual-directories

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

Zulu — Wed, 08 Jul 2009 18:55:52 GMT

I am getting the following error after deploying my site(IIS).

I think problem is with connetionstring. PLEASE HELP..

ERROR ::

Server Error in '/Fed' Application.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'VOLLER\ASPNET'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

Sergey — Fri, 08 May 2009 01:18:06 GMT

Nice post.

Would it be better to use ASP.NET ISAPI and remove static file directories from wildcard map so static files are not read by ISAPI every time, and then implement your HttpCompressionModule so asp.net mvc files get compressed?

blog.codeville.net/.../overriding-iis6-wildcard-maps-on-individual-directories

Why no support for "If-Modified-Since" header?

sean — Sun, 26 Apr 2009 12:26:41 GMT

Hi Omar,

Thank you for the nice piece of code. However, how come you did not check for the "If-Modified-Since" header? That way, you just need to send back a 304 to the client instead of the entire file all over again. I've described how to do this in my6solutions.com/.../Enabling-client-side-caching-on-ASP-NET-MVC-on-IIS-60.aspx.

Or is there something I'm missing?

Sean

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

Joel Nylund — Thu, 02 Apr 2009 20:20:18 GMT

Hi, what I am seeing is that compression is working for my static files but caching is not when I have wildcard mapping. If I disable wildcard mapping then everything works.

I tried your approach and it doesnt work for me, I get a bunch of bytes rendered on the html page (I think maybe its being double compressed) Do I need to turn off compression somewhere on IIS to do this?

If I remove the compression module the page gets served but with lots of errors.

Any ideas/suggestions why I am seeing slightly different behavior? Is it possible MS patched something since then that changes this a bit?

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

omar — Wed, 25 Mar 2009 11:06:57 GMT

You can turn on static file compression on IIS 7. I saw there was some config to change on IIS. Forgot.

IIS7?

Sparhawk — Wed, 25 Mar 2009 10:33:51 GMT

Hi,

I tried the solution. On my development server it works beautifully.

On the production server the compression works for .aspx and .asmx but not for .js and .css.

I am assuming that the StaticFileHandler is not used at all by IIS7.

Any ideas?

Sparhawk

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

Raphael — Fri, 06 Feb 2009 17:24:44 GMT

Hi Omar,

Wonderful tutorial here. Just a doubt: Does it work with all versions of ASP.NET mvc? I have a site developed around the preview 2, so would this work on it?

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

Meysam — Mon, 19 Jan 2009 10:06:49 GMT

Hi Zabir,

Given we don't want to compress image files, why don't you simply remove ".png", ".jpeg", ".jpg", ".gif" & ".bmp" extensions from FILE_TYPES so that they get bypassed and handled and cached by IIS?

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

Vladimir — Tue, 13 Jan 2009 18:33:24 GMT

How I can get it with IIS7? It's doesn't work properly. Please, wrote strings in web.config I must change.

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

prabhjot singh — Wed, 03 Dec 2008 08:44:14 GMT

Sir,

I am not using the MVC approach. After deploying the site on the server and implementing everything what you discussed in your earlier article, The "Resource not found" error is thrown. what should i do??

Regards

Prabhjot

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

jorgebg — Mon, 24 Nov 2008 13:27:17 GMT

Hi Omar,

Great job!

One small detail, I think there is a mistake on the method you use for "non-handled" extensions:

I removed the compressiontype parameter of the TransmitFileUsingHttpResponse in the lines below.

private void TransmitFileUsingHttpResponse(HttpRequest request, HttpResponse response,

string physicalFilePath, FileInfo file)

{

if (file.Exists)

{

// We don't cache/compress such file types. Must be some binary file that's better

// to let IIS handle

this.ProduceResponseHeader(response, Convert.ToInt32(file.Length), ResponseCompressionType.None,

physicalFilePath, file.LastWriteTimeUtc);

response.TransmitFile(physicalFilePath);

Debug.WriteLine("TransmitFile: " + request.FilePath);

}

else

{

throw new HttpException((int)HttpStatusCode.NotFound, request.FilePath + " Not Found");

}

Kind Regards!

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

Ricardo Cavalcanti — Wed, 12 Nov 2008 18:53:45 GMT

How do I set StaticFileHandler up in IIS 7?

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

Niran — Fri, 15 Aug 2008 10:16:24 GMT

Doesn't applying url format like

"{controller}/{action}/{id}.aspx"

solve such issues?

I am still very new to asp.net mvc. And is using this type of url format. This solution will work in shared hosts also.

Nirandas

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

omar — Fri, 11 Jul 2008 17:28:10 GMT

Hi Steve,

Thanks for the pointer. As I use a Response Filter to compress dynamic page output, so in my case, the DefaultHttpHandler calls StaticFielHandler to handle it. So, IIS 6 does not handle the file. This is why I made my custom Static File handler.

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

Steve Sanderson — Fri, 11 Jul 2008 15:57:55 GMT

Hi Omar

> Mapping wildcard extension to ASP.NET introduces the following problems...

I don't think this is always true. If you avoid interfering with the request, then DefaultHttpHandler leaves the request unhandled, which means IIS comes back in and serves the file natively (and then you'll get all the expiration headers etc.). The problems you describe only apply when DefaultHttpHandler serves the request through StaticFileHandler.

For details of how it chooses what to do, see sticklebackplastic.com/.../The+continuing+saga+of+StaticFileHandler++meet+DefaultHttpHandler.aspx

Thanks for writing this blog post though; it has lots of nice ideas.

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

omar — Fri, 04 Jul 2008 13:30:35 GMT

Hi Kazi,

I believe there's a confusion here. I haven't done caching for dynamic requests. My module is only for enabling compression site wide which does not have Action/Controller specific requirement.

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

Kazi Manzur Rashid — Fri, 04 Jul 2008 12:56:48 GMT

Hi Omar, as Mehfuz said I see a number of benifits of Action Filters over HttpModules, but before that just want to correct that You can apply the action filter on the Controller which in turn applies to all the action/public methods, it is not required to decorate method.

1. I do not have to stick with a Fixed Cache Duration.

2. Unable to exclude or need to have some kind of rule engine to exclude it from caching.

3. One of the main reason of MVC becoming so poplular is TDD, with HTTPModules it is harder and sometime impossible to fit in TDD.

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

omar — Wed, 02 Jul 2008 06:52:03 GMT

Hi Mehfuz,

ActionFilter is a great way to selectively enable compression on some requests. My solution turns on compression for all requests. This way you don't need to include the filter attribute on all action methods.

re: Deploy ASP.NET MVC on IIS 6, solve 404, compression and performance problems

Scott Hanselman — Wed, 02 Jul 2008 05:06:52 GMT

Fantastic post!