Migrating from IIS6 to IIS7, 404's, Handler mapping woes..
Hello, I've migrated an application from IIS 6 to IIS 7 and all is running well. I would like to handle 404 errors outside of ColdFusion however. Very simple with IIS 6, I simply checked "Verify that file exists" under the .cfm and .cfc extensions. In IIS 7, I have taken the route recommended in other forums by setting the "Invoke handler only if request is mapped to: File", but this has no effect on the processing of a ColdFusion template. I still see the generic 404 error that ColdFusion generates by default.
I've noticed that there is a wildcard declaration in the handler mappings, mapping all requests to jrun_iis6_wildcard.dll. I tried removing this entry and as soon as I do I get server errors for all of my requests. The fact that there is a change however is leading me to believe that this wildcard declarion is handling the .cfm requests, and not the handler actually assigned to *.cfm. The wildcard script mapping does not have the option mentioned above, so I cannot verify the ColdFusion template actually exists.
Viewing the "ordered list", *.cfm appears above the wildcard mapping, but I am expecting that because I've set the *.cfm mapping to execute only if the file exists, the request is simply dropping down to the wildcard mapping.
Anyone have luck with this?
AdChoices