Formerly, in IIS you could check a box that told IIS to not check first if a page exists on the .cfm extension, which would defeat IIS handling .cfm 404 errors. From there your CF 404 error template would take over. This behavior changed as IIS was upgraded. So Item 1: If you are using an earlier version of IIS the solution is different. Your version?
Look at this: http://stackoverflow.com/questions/18879758/coldfusion-10-update-11-404-handler-not-firing this was part of my discovery that CF 10/Win2k8 error handling was different from CF9/Win2k3. From this, thre observation that IIS was returning as the failed url http://[mydomain]:80/jakarta/isapi_redirect.dll became a CF bug that I am pretty sure got fixed. My eventual solution was posted up here http://stackoverflow.com/questions/18237478/iis7-displays-both-its-own-404-message-cf9-message-should-display-just-its-ow/18927484#18927484 and involved using a local site 404 template handler rather than one specified in the CF admin. If you follow the two discussions there were a lot of suggestions that wound up doing half the job, or an unacceptable version (IIS + CF errors shown, 200 codes returned) but the above fixed the lot. -- --m@Robertson-- Janitor, The Robertson Team mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:360092 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
