Comments on: Image Resizer – Configuring IIS

By: Nathanael Jones

Nathanael Jones — Thu, 27 May 2010 10:55:03 +0000

Open the ashx handler mapping in iis6 and uncheck 'verify file exists'.

By: Philippe Tremblay

Philippe Tremblay — Thu, 27 May 2010 01:06:47 +0000

Your product works fine on my dev platform (.Net3.0) but I can't make it work in my production environment (IIS6 and .Net 2.0). The Web Config file seems to be well configured, but I always have the “Page not found” when I’m trying URL such as http://icilocal.ca/Images/cies/Annonces/250043.jp... . Any idea?

By: Nathanael Jones

Nathanael Jones — Sat, 20 Feb 2010 18:58:00 +0000

Individual mappings seem to be very problematic… If wildcard mapping isn't an option, I'd suggest the .ashx/.axd alternative syntax…

Every version of IIS seems to be buggy regarding individual mappings…

There are a few things you could try… make sure NTFS permissions on both the image and the imagecache folder are set properly for both the IIS account AND the ASP.NET account. Verify the mapping is a script engine mapping… Check your URL authorization in web.config for bugs, and verify Anonoymous authentication works properly.

By: Cult

Cult — Fri, 19 Feb 2010 20:51:16 +0000

I'm using webhost4life, which I think is running IIS6. They have a control panel option to add a script map for *.jpg to go to ASP.NET, but when I do that all requests to jpgs on the site forward to the login screen. Only the /admin path is secured through. I can actually see the jpgs appearing in the imagecache, so I know the module is running and working fine, it is just that ASP.NET thinks the request should be authenticated for some reason. Has anyone seen this happen before? Do you know what setting might cause that to occur?

By: Nathanael Jones

Nathanael Jones — Fri, 20 Nov 2009 14:39:34 +0000

Thanks! I’ve corrected the documention to include 64-bit… Somehow I completely overlooked that situation when writing this article.

By: Simon

Simon — Fri, 20 Nov 2009 08:32:40 +0000

We had everything working on our 32bit II7 install using

add name=”ASPNET” path=”*” verb=”*” modules=”IsapiModule” scriptProcessor=”%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll” resourceType=”Unspecified” requireAccess=”None” preCondition=”classicMode,runtimeVersionv2.0,bitness32″

But when we deployed onto our 64 bit IIS7 sever we needed to change the settings to

add name=”ASPNET” path=”*” verb=”*” modules=”IsapiModule” scriptProcessor=”%windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll” resourceType=”Unspecified” requireAccess=”None” preCondition=”classicMode,runtimeVersionv2.0,bitness64″

This is not realy my area, but the changes seem to work….

By: Johnny

Johnny — Fri, 13 Nov 2009 14:59:01 +0000

Hi Nethanael,

Was just setting up the component on IIS7 in clasic mode and copied the above web.config line which errored due to the capitalization of some of the paramter names i.e scriptprocessor should be scriptProcessor.

The whole line should be: